activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AMQ-3841) mKahaDB causes ArrayIndexOutOfBoundsException on restart after deleting existing queues
Date Tue, 22 May 2012 19:49:41 GMT

     [ https://issues.apache.org/jira/browse/AMQ-3841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Timothy Bish resolved AMQ-3841.
-------------------------------

       Resolution: Fixed
    Fix Version/s: 5.7.0

Fixed in trunk test updated to show that a destination can be removed and then later re-added
without issue.
                
> mKahaDB causes ArrayIndexOutOfBoundsException on restart after deleting existing queues
> ---------------------------------------------------------------------------------------
>
>                 Key: AMQ-3841
>                 URL: https://issues.apache.org/jira/browse/AMQ-3841
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.6.0
>         Environment: Windows 7, JDK 6
>            Reporter: Matt Altermatt
>             Fix For: 5.7.0
>
>         Attachments: AMQ3841Test.java, output.txt
>
>
> To replicate, use these settings in the activemq.xml
> {code}
> 		<persistenceAdapter>
> 			<mKahaDB directory="${activemq.data}/kahadb">
> 				<filteredPersistenceAdapters>
> 					<filteredKahaDB perDestination="true" >
> 						<persistenceAdapter>
> 							<kahaDB journalMaxFileLength="32mb" />
> 						</persistenceAdapter>
> 					</filteredKahaDB>
> 				</filteredPersistenceAdapters>
> 			</mKahaDB>
> 		</persistenceAdapter>
> {code}
> # Start the broker
> # Create a queue
> #* This will create the queue in the /kahadb folder
> # Delete the queue
> #* The queue is not deleted from the /kahadb folder
> # Stop the broker
> # 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.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message