[AMQ-3357] vmQueueCursor or fileQueueCursor with expired messages in the store can lead to startup hang with kahaDB

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.4.2, 5.5.0
• Fix Version/s: 5.6.0
• Component/s: Message Store
• Labels: expiry fileQueueCursor hang kahadb restart vmQueueCursor
• Assignee: Gary Tully
• Reporter: Gary Tully
• Created: 03/Jun/11 12:23
• Updated: 02/May/13 02:29
• Resolved: 03/Jun/11 12:25

Description

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.

Issue Links

• is depended upon by: AMQ-3293 ActiveMQ broker hangs after sending many large messages with a TTL, and no DLQ