[
https://issues.apache.org/jira/browse/AMQ-3210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-3210.
-----------------------------
Resolution: Incomplete
Fix Version/s: 5.6.0
Marking this as incomplete as there is no test case and the suggested comments
should help.
If the index is out of sync w.r.t the journal, just deleting the index, db.data
is sufficient to have the index rebuild automatically on restart, by replaying
the journal.
> OutOfMemory error on ActiveMQ startup
> -------------------------------------
>
> Key: AMQ-3210
> URL: https://issues.apache.org/jira/browse/AMQ-3210
> Project: ActiveMQ
> Issue Type: Bug
> Components: Message Store
> Affects Versions: 5.4.2
> Environment: # java -version
> java version "1.6.0_18"
> OpenJDK Runtime Environment (IcedTea6 1.8.3) (6b18-1.8.3-2~lenny1)
> OpenJDK Client VM (build 16.0-b13, mixed mode, sharing)
> # cat /etc/debian_version
> 5.0.8
> Reporter: Lior Okman
> Priority: Critical
> Fix For: 5.6.0
>
> Attachments: activemq.xml, exception.log, kahadb.tar.bz2
>
>
> Probably due to some kind of message store corruption, when trying to start
> ActiveMQ, I get OutOfMemory errors and the startup simply fails.
> This can be solved by deleting /var/local/apache-activemq/kahadb, after which
> ActiveMQ starts with no issue.
> This issue doesn't always happen, and I'm not sure of a scenario that can
> reproduce this. I do have a corrupted kahadb directory that reproduces the
> problem.
--
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
