[AMQ-3841] mKahaDB causes ArrayIndexOutOfBoundsException on restart after deleting existing queues

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.6.0
• Fix Version/s: 5.7.0
• Component/s: Broker

Environment

Windows 7, JDK 6

• Assignee: Timothy A. Bish
• Reporter: Matt Altermatt
• Created: 15/May/12 18:26
• Updated: 31/May/12 15:35
• Resolved: 22/May/12 19:48

Description

To replicate, use these settings in the activemq.xml

		<persistenceAdapter>
			<mKahaDB directory="${activemq.data}/kahadb">
				<filteredPersistenceAdapters>
					<filteredKahaDB perDestination="true" >
						<persistenceAdapter>
							<kahaDB journalMaxFileLength="32mb" />
						</persistenceAdapter>
					</filteredKahaDB>
				</filteredPersistenceAdapters>
			</mKahaDB>
		</persistenceAdapter>

1. Start the broker
2. Create a queue
   • This will create the queue in the /kahadb folder
3. Delete the queue
   • The queue is not deleted from the /kahadb folder
4. Stop the broker
5. Start the broker

This will cause cause the stack trace that is attached.

To fix this, delete the queue in the /kahadb folder and start the broker. This allows the broker to start as normal.