[
https://issues.apache.org/jira/browse/AMQ-2962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish closed AMQ-2962.
-----------------------------
Resolution: Cannot Reproduce
Issue appears to be fixed on trunk, suggest testing with 5.6 SNAPSHOT. If you
still see the issue, a JUnit test cases demonstrating the issue would be
useful.
> Hanging at startup
> ------------------
>
> Key: AMQ-2962
> URL: https://issues.apache.org/jira/browse/AMQ-2962
> Project: ActiveMQ
> Issue Type: Bug
> Components: Message Store
> Affects Versions: 5.4.1
> Environment: Fedora Core 12
> OracleSun java 1.6:
> java version "1.6.0_21"
> Java(TM) SE Runtime Environment (build 1.6.0_21-b06)
> Java HotSpot(TM) 64-Bit Server VM (build 17.0-b16, mixed mode)
> JBoss 4.2.3 using AMQ resource adapter.
> Reporter: Roelof Naude
> Attachments: AMQ2962.patch, amq.ra.threads.txt,
> debug_traces_hanging.log, debug_traces_startup.log,
> thread_dump_during_hang.txt
>
>
> Noticed today the activemq was hanging during startup. Investigation revealed
> that it is tied to expiration of messages at startup. The only way to recover
> from this was to kill -9 the VM and delete the kahadb message store.
> Further testing was done whereby message expiry time was set to longer
> period. AMQ started up just fine. Another test was performed whereby:
> 1. subscribe for messages
> 2. send a few messages
> 3. disconnect consumer
> 4. send more messages (1 or 2 will do)
> 5. shutdown AMQ
> 6. wait for a time period exceeded the expiration time of the messages
> 7. start AMQ. at this time it should be hanging
> Logs and thread dumps attached.
--
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
