Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Tue, 20 Sep 2011 09:45:10 +0000 (UTC)
From: "Lior Okman (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: 
 <2080979396.45534.1316511910169.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1547779918.4536.1299595019359.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (AMQ-3210) OutOfMemory error on ActiveMQ startup
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/AMQ-3210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13108482#comment-13108482 ] 

Lior Okman commented on AMQ-3210:
---------------------------------

Still checking. 

Since I don't have a scenario to recreate the issue and the issue doesn't always happen, I can't say for sure if the configuration change fixed it. 

> 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