activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Tully (JIRA)" <j...@apache.org>
Subject [jira] [Created] (AMQ-3357) vmQueueCursor or fileQueueCursor with expired messages in the store can lead to startup hang with kahaDB
Date Fri, 03 Jun 2011 12:24:47 GMT
vmQueueCursor or fileQueueCursor with expired messages in the store can lead to startup hang
with kahaDB
--------------------------------------------------------------------------------------------------------

                 Key: AMQ-3357
                 URL: https://issues.apache.org/jira/browse/AMQ-3357
             Project: ActiveMQ
          Issue Type: Bug
          Components: Message Store
    Affects Versions: 5.5.0, 5.4.2
            Reporter: Gary Tully
            Assignee: Gary Tully
             Fix For: 5.6.0


expiry during recovery, which is a read operation, can lead to the need to modify the store.
The recovery processing should take out a readwrite lock on the store.

Issue arises for vm or file cursors as they replay messages from the store on restart to fill
their caches. 
This issue can be avoided by using the default Store cursor, so the workaround is to configure
the store cursor, restart, and revert back to the chosen cursor.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message