Keith Wall created QPID-6214:
--------------------------------

             Summary: Stopping a virtualhost that has in-flight asynchronous 
message store recovery can lead abnormal broker shutdown
                 Key: QPID-6214
                 URL: https://issues.apache.org/jira/browse/QPID-6214
             Project: Qpid
          Issue Type: Bug
          Components: Java Broker
    Affects Versions: 0.30
            Reporter: Keith Wall
             Fix For: 0.31


Stopping a VH that has an in-flight asynchronous message store recovery can 
lead to the following stack trace and the Broker shutting down abnormally.

This problem can also occur spontaneously in the HA case if a master change 
occurs whilst asynchronous recovery is in progress.

The async recovery is off by default so users can only see this problem if they 
have enabled use_async_message_store_recovery.

{noformat}
java.lang.IllegalStateException: Message store is not open
at 
org.apache.qpid.server.store.berkeleydb.BDBConfigurationStore$ProvidedBDBMessageStore.checkMessageStoreOpen(BDBConfigurationStore.java:595)
at 
org.apache.qpid.server.store.berkeleydb.AbstractBDBMessageStore.visitMessages(AbstractBDBMessageStore.java:171)
at 
org.apache.qpid.server.virtualhost.AsynchronousMessageStoreRecoverer$AsynchronousRecoverer.completeRecovery(AsynchronousMessageStoreRecoverer.java:153)
at 
org.apache.qpid.server.virtualhost.AsynchronousMessageStoreRecoverer$AsynchronousRecoverer.recoverQueue(AsynchronousMessageStoreRecoverer.java:140)
at 
org.apache.qpid.server.virtualhost.AsynchronousMessageStoreRecoverer$AsynchronousRecoverer.access$800(AsynchronousMessageStoreRecoverer.java:68)
at 
org.apache.qpid.server.virtualhost.AsynchronousMessageStoreRecoverer$AsynchronousRecoverer$QueueRecoveringTask.run(AsynchronousMessageStoreRecoverer.java:367)
at java.lang.Thread.run(Thread.java:745)
{noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to