You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@activemq.apache.org by t-watana <wa...@jp.fujitsu.com> on 2019/02/05 06:58:50 UTC

The timeout of offline durable subscriber when ActiveMQ restarting

I'm using ActiveMQ 5.13.1.

I want to know the reason why the "offlineTimestamp in
DurableTopicSubscription.java" 
seems to be set only on memory, not persistent storage (like KahaDB).

If restarting ActiveMQ, the "offlineTimestamp" is reset to "-1".
So, it seems that the AMQ can't execute timeout of 
offline durable subscriber in according with the property 
"offlineDurableSubscriberTimeout" in activemq.xml.

the relevant code is followed ( from TopicRegion#doCleanUp() )


Why is the "offlineTimestamp" not persisted ?
Looking forward to your reply.




--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-Dev-f2368404.html