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 wrote:
>Thanks for your answe
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 u
The checkpoint process is trying to write the index but it's having some
issue writing to your networked drive:
java.io.IOException: network path not found
On Fri, Mar 8, 2013 at 9:46 AM, jcamus wrote:
> Hi!
> Am using ActiveMq to store files to be processed. I had the following logs,
> when I
Hi!
Am using ActiveMq to store files to be processed. I had the following logs,
when I restart my applications, I have still the problem (no files in the
queue are consumed), the only way is to purge the activemq data directory.
But all the files are definitely lost!
2013-03-06 22:09:58,423 ERROR [
