Hi, Tim ! Yes. I'm using 5.13.1.
I will try debugging and check the location size. In this case, my KahaDB size is very large. It seems that the message in which the offlineDurableSubscriberTimeout occurred has not been deleted, so I restart ActiveMQ then this trouble is occrred. Do you think that the message is not deleted also because KahaDB location size is broken? -- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
