Re: offlineDurableSubscriberTimeout in artemis

2023-04-18 Thread Justin Bertram
You need true because subscription queues for durable JMS subscribers are not technically considered auto-created. Keep in mind that addresses and queues are independent. Just because an address is auto-created doesn't necessarily mean that a queue is. Generally speaking, it's totally fine to use

Re: offlineDurableSubscriberTimeout in artemis

2023-04-18 Thread Thai Le
Thanks Justin, It works, but i am not sure why i need true, my queues are auto created, and i can see from web console that their address has AutoCreated=true. Regarding the specific addressSettings for queues, i am trying to do that but some of my jms destination uses "." separation like QUEUE.se

Re: offlineDurableSubscriberTimeout in artemis

2023-04-18 Thread Justin Bertram
I think this should work: true true 30 -1 true However, I *strongly* recommend you use a very specific address-setting match value with these settings. Your current settings are using "#" which will apply to *all* addresses and those settings will delete *any* auto-create

Re: offlineDurableSubscriberTimeout in artemis

2023-04-18 Thread Thai Le
Thank you for quick response. -Some of our application are python using STOMP protocol to listen to queue, the others are spring boot app and listening to queue using JmsListener and their application.propeties has spring.artemis.mode=native so I assume they are using CORE. -I am currently testing

Re: offlineDurableSubscriberTimeout in artemis

2023-04-18 Thread Justin Bertram
You should be able to remove the subscription queue with the right combination of address-settings. I've got a few questions to clarify the use-case a bit: - What protocol is the durable subscriber using? - What version of ActiveMQ Artemis are you using? - What are all of your existing address-