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:
...
I forgot to include this for the configuration where you want to
automatically delete queues from durable JMS subscriptions:
true
Justin
On Tue, Oct 10, 2023 at 8:46 AM Justin Bertram wrote:
> Yes. You can use a combination of the following address-settings:
>
> -
> -
> -
>
> For exam
> The broker shouldn’t delete a queue associated to shared durable
subscriptions even if no consumers are active at that moment and should
store all the messages in the meanwhile. Am I right?
You are correct. However, it appears to me that you've actually configured
the broker to override the defa
Hello,
my issue is not completely bound to Artemis (involves Camel also) so I’m
trying to ask here first.
>From the JMS specs 2.0 and AMQP I found, the behavior of the shared durable
>subscriptions is still the same as for JMS 1.x specs.
The broker shouldn’t delete a queue associated to sha
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
Yes. You can use a combination of the following address-settings:
-
-
-
For example, if you wanted to remove queues (e.g. from durable
subscriptions) on the address "myTopic" (e.g. that was being used as a JMS
topic) then you might configure something like this:
true
36
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
Hi,
If there a way in Artemis broker to automatically remove inactive durable topic
subscribers. E.g. check every hour of inactive subscribers and remove the one
who are not active for last 12 hours.
Classic ActiveMQ has some configuration
(https://activemq.apache.org/manage-durable-subscribers
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'
10 matches
Mail list logo