I finally managed to understand why I got the problems described earlier.
The "producer" uses "artemis-jms" while the deployed MDB uses "artemis-ra".
Both components uses
org.apache.activemq.artemis.core.client.impl.ClientSessionImpl.createQueue(…).
However, "artemis-ra" tries to create the que
I tried to deploy a MDB to a Wildfly 28 server but I still get the same
problems (however, the logging looks a little bit different on this server).
This was added to standalone-full.xml:
...
My only guess at this point is that there's bug or something in the client
you're using. WildFly 20 shipped with ActiveMQ Artemis 2.10.1 which is over
4 years old now. That version of WildFly is itself over 3 years old. Any
chance you could test on a more recent version of WildFly?
Justin
On Tue
Thanks for the reply,
However, I had alread added it to my acceptor before my failing attempts:
tcp://0.0.0.0:61616?anycastPrefix=jms.queue.;multicastPrefix=jms.topic.;tcpSendBufferSize=1048576;tcpReceiveBufferSize=1048576;amqpMinLargeMessageSize=102400;protocols=CORE,AMQP,STOMP,HORNETQ,MQTT,OPENW
The fact that your client is running on WildFly is an important detail
because it still uses the 1.x prefixes for JMS queues and topics (i.e.
"jms.queue." and "jms.topic" respectively). Therefore, you should try
adding this to your acceptor:
anycastPrefix=jms.queue.;multicastPrefix=jms.topic.
L
Thanks for the reply,
I'm using ActiveMQ Artemis 2.31.0 as well.
Thanks for the suggestion on using the "consumer" and "producer" commands (I
didn't know of them). However, when using the commands everything worked as
expected (using my intended Artemis configuration).
I assume my problem isn'
Given the modifications you've made I would expect your JMS consumer to be
able to use the queue. I did a quick proof-of-concept on my own machine
with all the same changes you made and it works fine using the "consumer"
and "producer" commands shipped with the broker (which use JMS). Nothing is
au
Hi,
Is there anyone who could confirm if it is possible to configure Artemis in the
same way as I explained in my previous mail or if I have misunderstood the
whole things.
Thanks in advance,
Calle
Från: Calle Andersson
Skickat: torsdag, oktober 5, 2023 1:55:1
