Return-Path: 
 <dev-return-28215-apmail-activemq-dev-archive=activemq.apache.org@activemq.apache.org>
X-Original-To: apmail-activemq-dev-archive@www.apache.org
Delivered-To: apmail-activemq-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 08F1C77EB
	for <apmail-activemq-dev-archive@www.apache.org>;
 Tue, 23 Aug 2011 12:40:01 +0000 (UTC)
Received: (qmail 87102 invoked by uid 500); 23 Aug 2011 12:40:00 -0000
Delivered-To: apmail-activemq-dev-archive@activemq.apache.org
Received: (qmail 85910 invoked by uid 500); 23 Aug 2011 12:39:54 -0000
Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@activemq.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@activemq.apache.org>
List-Post: <mailto:dev@activemq.apache.org>
List-Id: <dev.activemq.apache.org>
Reply-To: dev@activemq.apache.org
Delivered-To: mailing list dev@activemq.apache.org
Received: (qmail 85893 invoked by uid 99); 23 Aug 2011 12:39:53 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Aug 2011 12:39:53 +0000
X-ASF-Spam-Status: No, hits=-2000.9 required=5.0
	tests=ALL_TRUSTED,RP_MATCHES_RCVD
X-Spam-Check-By: apache.org
Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Aug 2011 12:39:50 +0000
Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116])
	by hel.zones.apache.org (Postfix) with ESMTP id 32551CB66E
	for <dev@activemq.apache.org>; Tue, 23 Aug 2011 12:39:29 +0000 (UTC)
Date: Tue, 23 Aug 2011 12:39:29 +0000 (UTC)
From: "Sree Panchajanyam D (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: 
 <1831549216.5035.1314103169203.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
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
X-Virus-Checked: Checked by ClamAV on apache.org


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

Sree Panchajanyam D commented on AMQ-3210:
------------------------------------------

Corrupt journal files can be identified but not corrupt metadata.
You can ensure that the metadata is synced up regularly by setting the parameters "indexWriteBatchSize" and "checkpointInterval" to practically low values. Take a look at the documentation for these parameters at below links:
http://activemq.apache.org/kahadb.html
http://fusesource.com/docs/broker/5.5/persistence/index.html ( Optimizing the Metadata Cache)
Metadata is not synced with the cache during server crashes. 
Hence, the best thing to do is to prevent ActiveMQ from crashing. 
I see that in your xml you have used producer flow control I would advocate against it if you are not sure why you need it.
If you are using persistent messages use them with a time to live. Allocate store space with  following caluculation  "store space = no. of messages/second * avg message size  * time to live * 2".
For non-persistent messages the above calc. will not hold good.

PS: in activemq.xml
        <persistenceAdapter>
            <kahaDB directory="${activemq.base}/data/kahadb"/>
			<kahaDB checkForCorruptJournalFiles="true"/>
			<kahaDB checksumJournalFiles="true"/>
			<kahaDB indexWriteBatchSize="1000"/>
                              <kahaDB checkpointInterval="1000"/>
        </persistenceAdapter>


> 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