Hello,

I've lost messages following this configuration/scenario, but I'm not able
to reproduce this problem again, so I am asking for information about the
recovery process from the Journal in case the database was not able to
persist pending messages.
Here is the scenario:
1 - ActiveMQ server is running, persistence is activated, using a started
Derby database
2 - Messages are written to a queue
3 - Database is shutdown
4 - ActiveMQ is shutdown
5 - Database is started
6 - ActiveMQ is started
Following this scenario, every messages from the queue were disappeared
(nothing in database, nothing in queue, we are able to read part of messages
in the journal but not able to read a specific status).

Is there a possibility that messages writen in activeMQ had a particular
status and no recovery from the journal was possible? The expected behavior
is that at the activeMQ startup, the last non persisted operations from the
journal should be persisted in database?

For information, in activeMQ logs I had this error saying that at step 3 no
persistence was possible (but this looks normal since database is down):
ERROR - Failed to checkpoint a message store:
edu.emory.mathcs.backport.java.util.concurrent.ExecutionException:
java.lang.NullPointerException
edu.emory.mathcs.backport.java.util.concurrent.ExecutionException:
java.lang.NullPointerException
        at
edu.emory.mathcs.backport.java.util.concurrent.FutureTask.getResult(FutureTask.java:299)
        at
edu.emory.mathcs.backport.java.util.concurrent.FutureTask.get(FutureTask.java:118)
        at
org.apache.activemq.store.journal.JournalPersistenceAdapter.doCheckpoint(JournalPersistenceAdapter.java:386)
        at ...(see attached log file for more log trace) 
steform.43_start
<http://activemq.2283324.n4.nabble.com/file/n4710175/steform.43_start>  



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/Active-MQ-4-1-2-Recovery-after-persistence-database-shutdown-tp4710175.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Reply via email to