If only the index files are stale you can try to remove all index files (*.data) and restart the broker to rebuild the index. The broker will get stopped when IO exception occurs so new messages are unable to enqueue the broker in fact.
At 2013-03-10 00:59:13,jcamus <[email protected]> wrote: >Thanks for your answer. But how to explain that data is totally lost? The >only way to have activemq working again normally is to purge the data >directory. But unfortunately all data is lost. Activemq seems not detecting >that there is a problem and it is still accepting new message to enqueue, >but unable to process them properly. I guess we have a problem with our >network, or our windows sever, but I am totally astonished not to have >Activemq refusing each file to be enqueued. > >Regards. > > > > > >-- >View this message in context: >http://activemq.2283324.n4.nabble.com/Data-loss-with-ActiveMQ-5-6-0-tp4664521p4664564.html >Sent from the ActiveMQ - User mailing list archive at Nabble.com.
