Return-Path: 
 <dev-return-36137-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 7A384EC61
	for <apmail-activemq-dev-archive@www.apache.org>;
 Wed, 30 Jan 2013 14:59:14 +0000 (UTC)
Received: (qmail 86108 invoked by uid 500); 30 Jan 2013 14:59:14 -0000
Delivered-To: apmail-activemq-dev-archive@activemq.apache.org
Received: (qmail 85927 invoked by uid 500); 30 Jan 2013 14:59:14 -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 85906 invoked by uid 99); 30 Jan 2013 14:59:13 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 Jan 2013 14:59:13 +0000
Date: Wed, 30 Jan 2013 14:59:13 +0000 (UTC)
From: "mauro rappa (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: <JIRA.12629911.1359557783459.215527.1359557953694@arcas>
In-Reply-To: <JIRA.12629911.1359557783459@arcas>
References: <JIRA.12629911.1359557783459@arcas>
Subject: [jira] [Updated] (AMQ-4284) KahaDBSTore reset batching
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


     [ https://issues.apache.org/jira/browse/AMQ-4284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

mauro rappa updated AMQ-4284:
-----------------------------

    Description: 
I'm using apache-activemq-5.6.0 on Centos 6.3 with persistence configured as:

<kahaDB directory="${activemq.data}/kahadb"  checksumJournalFiles="true" checkForCorruptJournalFiles="true" cleanupInterval="10000" journalMaxFileLength="64mb" checkpointInterval="3000" maxAsyncJobs="1000" archiveDataLogs="false" directoryArchive="${activemq.data}/kahadb/consumed"/>

all MQ instance is running on a SAN partition (  type ext4 option rw,journal_ioprio=0,max_batch_time=5000,data=journal )

but during some load tests is saw few times this error:

2013-01-29 13:25:56,511 | ERROR | Failed to reset batching | org.apache.activemq.store.kahadb.KahaDBStore | ActiveMQ ShutdownHook
java.lang.IllegalStateException: PageFile is not loaded
        at org.apache.kahadb.page.PageFile.assertLoaded(PageFile.java:800)
        at org.apache.kahadb.page.PageFile.tx(PageFile.java:294)
        at org.apache.activemq.store.kahadb.KahaDBStore$KahaDBMessageStore.resetBatching(KahaDBStore.java:575)
        at org.apache.activemq.store.ProxyMessageStore.resetBatching(ProxyMessageStore.java:111)
        at org.apache.activemq.broker.region.cursors.QueueStorePrefetch.resetBatch(QueueStorePrefetch.java:85)
        at org.apache.activemq.broker.region.cursors.AbstractStoreCursor.stop(AbstractStoreCursor.java:72)
        at org.apache.activemq.broker.region.cursors.StoreQueueCursor.stop(StoreQueueCursor.java:84)
        at org.apache.activemq.broker.region.Queue.stop(Queue.java:909)
        at org.apache.activemq.broker.region.AbstractRegion.stop(AbstractRegion.java:118)
        at org.apache.activemq.util.ServiceStopper.stop(ServiceStopper.java:41)
        at org.apache.activemq.broker.region.RegionBroker.doStop(RegionBroker.java:713)
        at org.apache.activemq.broker.jmx.ManagedRegionBroker.doStop(ManagedRegionBroker.java:122)
        at org.apache.activemq.broker.region.RegionBroker.stop(RegionBroker.java:201)
        at org.apache.activemq.broker.BrokerFilter.stop(BrokerFilter.java:161)
        at org.apache.activemq.broker.BrokerFilter.stop(BrokerFilter.java:161)
        at org.apache.activemq.broker.TransactionBroker.stop(TransactionBroker.java:193)
        at org.apache.activemq.broker.BrokerService$3.stop(BrokerService.java:1961)
        at org.apache.activemq.util.ServiceStopper.stop(ServiceStopper.java:41)
        at org.apache.activemq.broker.BrokerService.stop(BrokerService.java:624)
        at org.apache.activemq.broker.BrokerService.containerShutdown(BrokerService.java:2162)
        at org.apache.activemq.broker.BrokerService$4.run(BrokerService.java:2129)


is it something known? any wrong tuning on my side?

  was:
I'm using apache-activemq-5.6.0 on Centos 6.3 with persistence configured as:

<kahaDB directory="${activemq.data}/kahadb"
 checksumJournalFiles="true" checkForCorruptJournalFiles="true" cleanupInterval="10000" journalMaxFileLength="64mb" 
checkpointInterval="3000" maxAsyncJobs="1000" archiveDataLogs="false" 
directoryArchive="${activemq.data}/kahadb/consumed"/>

all MQ instance is running on a SAN partition (  type ext4 option rw,journal_ioprio=0,max_batch_time=5000,data=journal )

but during some load tests is saw few times this error:

2013-01-29 13:25:56,511 | ERROR | Failed to reset batching | org.apache.activemq.store.kahadb.KahaDBStore | ActiveMQ ShutdownHook
java.lang.IllegalStateException: PageFile is not loaded
        at org.apache.kahadb.page.PageFile.assertLoaded(PageFile.java:800)
        at org.apache.kahadb.page.PageFile.tx(PageFile.java:294)
        at org.apache.activemq.store.kahadb.KahaDBStore$KahaDBMessageStore.resetBatching(KahaDBStore.java:575)
        at org.apache.activemq.store.ProxyMessageStore.resetBatching(ProxyMessageStore.java:111)
        at org.apache.activemq.broker.region.cursors.QueueStorePrefetch.resetBatch(QueueStorePrefetch.java:85)
        at org.apache.activemq.broker.region.cursors.AbstractStoreCursor.stop(AbstractStoreCursor.java:72)
        at org.apache.activemq.broker.region.cursors.StoreQueueCursor.stop(StoreQueueCursor.java:84)
        at org.apache.activemq.broker.region.Queue.stop(Queue.java:909)
        at org.apache.activemq.broker.region.AbstractRegion.stop(AbstractRegion.java:118)
        at org.apache.activemq.util.ServiceStopper.stop(ServiceStopper.java:41)
        at org.apache.activemq.broker.region.RegionBroker.doStop(RegionBroker.java:713)
        at org.apache.activemq.broker.jmx.ManagedRegionBroker.doStop(ManagedRegionBroker.java:122)
        at org.apache.activemq.broker.region.RegionBroker.stop(RegionBroker.java:201)
        at org.apache.activemq.broker.BrokerFilter.stop(BrokerFilter.java:161)
        at org.apache.activemq.broker.BrokerFilter.stop(BrokerFilter.java:161)
        at org.apache.activemq.broker.TransactionBroker.stop(TransactionBroker.java:193)
        at org.apache.activemq.broker.BrokerService$3.stop(BrokerService.java:1961)
        at org.apache.activemq.util.ServiceStopper.stop(ServiceStopper.java:41)
        at org.apache.activemq.broker.BrokerService.stop(BrokerService.java:624)
        at org.apache.activemq.broker.BrokerService.containerShutdown(BrokerService.java:2162)
        at org.apache.activemq.broker.BrokerService$4.run(BrokerService.java:2129)


is it something known? any wrong tuning on my side?

    
> KahaDBSTore reset batching
> --------------------------
>
>                 Key: AMQ-4284
>                 URL: https://issues.apache.org/jira/browse/AMQ-4284
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Message Store
>    Affects Versions: 5.6.0
>            Reporter: mauro rappa
>              Labels: performance
>
> I'm using apache-activemq-5.6.0 on Centos 6.3 with persistence configured as:
> <kahaDB directory="${activemq.data}/kahadb"  checksumJournalFiles="true" checkForCorruptJournalFiles="true" cleanupInterval="10000" journalMaxFileLength="64mb" checkpointInterval="3000" maxAsyncJobs="1000" archiveDataLogs="false" directoryArchive="${activemq.data}/kahadb/consumed"/>
> all MQ instance is running on a SAN partition (  type ext4 option rw,journal_ioprio=0,max_batch_time=5000,data=journal )
> but during some load tests is saw few times this error:
> 2013-01-29 13:25:56,511 | ERROR | Failed to reset batching | org.apache.activemq.store.kahadb.KahaDBStore | ActiveMQ ShutdownHook
> java.lang.IllegalStateException: PageFile is not loaded
>         at org.apache.kahadb.page.PageFile.assertLoaded(PageFile.java:800)
>         at org.apache.kahadb.page.PageFile.tx(PageFile.java:294)
>         at org.apache.activemq.store.kahadb.KahaDBStore$KahaDBMessageStore.resetBatching(KahaDBStore.java:575)
>         at org.apache.activemq.store.ProxyMessageStore.resetBatching(ProxyMessageStore.java:111)
>         at org.apache.activemq.broker.region.cursors.QueueStorePrefetch.resetBatch(QueueStorePrefetch.java:85)
>         at org.apache.activemq.broker.region.cursors.AbstractStoreCursor.stop(AbstractStoreCursor.java:72)
>         at org.apache.activemq.broker.region.cursors.StoreQueueCursor.stop(StoreQueueCursor.java:84)
>         at org.apache.activemq.broker.region.Queue.stop(Queue.java:909)
>         at org.apache.activemq.broker.region.AbstractRegion.stop(AbstractRegion.java:118)
>         at org.apache.activemq.util.ServiceStopper.stop(ServiceStopper.java:41)
>         at org.apache.activemq.broker.region.RegionBroker.doStop(RegionBroker.java:713)
>         at org.apache.activemq.broker.jmx.ManagedRegionBroker.doStop(ManagedRegionBroker.java:122)
>         at org.apache.activemq.broker.region.RegionBroker.stop(RegionBroker.java:201)
>         at org.apache.activemq.broker.BrokerFilter.stop(BrokerFilter.java:161)
>         at org.apache.activemq.broker.BrokerFilter.stop(BrokerFilter.java:161)
>         at org.apache.activemq.broker.TransactionBroker.stop(TransactionBroker.java:193)
>         at org.apache.activemq.broker.BrokerService$3.stop(BrokerService.java:1961)
>         at org.apache.activemq.util.ServiceStopper.stop(ServiceStopper.java:41)
>         at org.apache.activemq.broker.BrokerService.stop(BrokerService.java:624)
>         at org.apache.activemq.broker.BrokerService.containerShutdown(BrokerService.java:2162)
>         at org.apache.activemq.broker.BrokerService$4.run(BrokerService.java:2129)
> is it something known? any wrong tuning on my side?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira