> I have created the queue using the element in the broker.xml.
And for some reason it created "Multicast" routing. Does it make any sense?
Yes, that makes sense. The legacy element in does not
support any way to specify a routing-type so it just defaults to multicast
which was the default ro
Thanks.
I finally managed to get it working on 2.4.0. I didn't even had to add that
two casePrefix acceptor parameters. It was indeed related to the "queue.jms"
prefix. But not only that.
It confused me the messages have header.address = "jms.queue.test". But the
broker is expecting just an "test
I think Artemis 1.4.x clients *should* be compatible with 2.x brokers, but
that's not to say there couldn't be a bug. Lots of work has been done
recently in the area of compatibility for the 2.5 release so you might try
building the master branch and trying that out (be sure to add
"anycastPrefix=
Is there a way to connect to the Artemis server (2.4.0) using JMS client on
JRE7?
Unfortunately I'm stuck with Java 7 on the client side. I tried to use jars
from the Artemis 1.4.4 (the latest one supporting jre7 I believe). But the
message always goes to DLQ. I have the destination auto-creation e
