[
https://issues.apache.org/jira/browse/AMQ-3210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13089393#comment-13089393
]
Lior Okman commented on AMQ-3210:
---------------------------------
Is there any way to identify this corruption on startup and purge the database
if it is identified, so that the ActiveMQ process can start without an operator
having to manually delete the KahaDB files?
> 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
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
