Tonight we got new experience with the problem: before we restart ActiveMQ we looked at the messages in a queue and we saw that the size of the queue was 0. After having restarted ActiveMQ we looked at the messages in the queue again and there were 4 messages from today morning. All 4 messages correspond to the timestamps of KahaDB file rotations: we see those files on the file system and we see that the last modification times of those files are the same time as the timestamps of the messages. After that we removed those messages manually from ActiveMQ via JMX Console and there were away and were not delivered at that run. But when we restarted ActiveMQ the second time, those 4 messages were again in the queue! So Remove via JMX did not removed them from the storage. Only after our consumer consumed and acknowledged those 4 messages, they disappeared completely and did not come with the next restart.
-- View this message in context: http://activemq.2283324.n4.nabble.com/ActiveMQ-5-10-looses-message-acknowledgements-tp4690306p4690308.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
