Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Fri, 16 Nov 2012 11:22:12 +0000 (UTC)
From: "Gary Tully (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: <380893294.123324.1353064932654.JavaMail.jiratomcat@arcas>
In-Reply-To: <1092232992.73520.1341006404379.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Commented] (AMQ-3906) repeated error message regarding
 chunk stream logged
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Gary Tully commented on AMQ-3906:
---------------------------------

good news.
yeah, sorry about that startup issue. There has been a bunch of new modules introduced on trunk so the snapshots are in a bit of flux... but that issue has been resolved. The snapshot from last night (apache-activemq-5.8-20121116.041126-35-bin.tar.gz) should be fine. 
                
> repeated error message regarding chunk stream logged
> ----------------------------------------------------
>
>                 Key: AMQ-3906
>                 URL: https://issues.apache.org/jira/browse/AMQ-3906
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.6.0
>         Environment: ActiveMQ 5.6.0 running on Linux FC10 x86
>            Reporter: Rajib Rashid
>         Attachments: activemq.xml, kahadb.zip
>
>
> after running normally for ~24 hours, warning messages/errors like below are logged every 30 seconds:
> {code}
> 2012-06-27 14:33:31,532 org.apache.activemq.broker.region.Topic[ActiveMQ Broker[ZyrionMessageBus] Scheduler]: (WARN) Failed to browse Topic: remoteUpdateP2PTopic
> java.io.EOFException: Chunk stream does not exist, page: 50 is marked free
>         at org.apache.kahadb.page.Transaction$2.readPage(Transaction.java:460)
>         at org.apache.kahadb.page.Transaction$2.<init>(Transaction.java:437)
>         at org.apache.kahadb.page.Transaction.openInputStream(Transaction.java:434)
>         at org.apache.kahadb.page.Transaction.load(Transaction.java:410)
>         at org.apache.kahadb.page.Transaction.load(Transaction.java:367)
>         at org.apache.kahadb.index.BTreeIndex.loadNode(BTreeIndex.java:262)
>         at org.apache.kahadb.index.BTreeIndex.getRoot(BTreeIndex.java:174)
>         at org.apache.kahadb.index.BTreeIndex.iterator(BTreeIndex.java:232)
>         at org.apache.activemq.store.kahadb.MessageDatabase$MessageOrderIndex$MessageOrderIterator.<init>(MessageDatabase.java:2714)
>         at org.apache.activemq.store.kahadb.MessageDatabase$MessageOrderIndex.iterator(MessageDatabase.java:2696)
>         at org.apache.activemq.store.kahadb.KahaDBStore$KahaDBMessageStore$3.execute(KahaDBStore.java:525)
>         at org.apache.kahadb.page.Transaction.execute(Transaction.java:769)
>         at org.apache.activemq.store.kahadb.KahaDBStore$KahaDBMessageStore.recover(KahaDBStore.java:521)
>         at org.apache.activemq.store.ProxyTopicMessageStore.recover(ProxyTopicMessageStore.java:62)
>         at org.apache.activemq.broker.region.Topic.doBrowse(Topic.java:559)
>         at org.apache.activemq.broker.region.Topic.access$100(Topic.java:62)
>         at org.apache.activemq.broker.region.Topic$6.run(Topic.java:684)
>         at org.apache.activemq.thread.SchedulerTimerTask.run(SchedulerTimerTask.java:33)
>         at java.util.TimerThread.mainLoop(Timer.java:512)
>         at java.util.TimerThread.run(Timer.java:462)
> {code}
> since then the warning has been logged 6000+ times. not sure if this is due to the fact that we have enabled expiration of queued messages for offline subscribers.
> {code}
> % ls -l apps/activemq/data/kahadb/
> total 32068
> -rw-r--r-- 1 root root 33030144 2012-06-29 14:44 db-14.log
> -rw-r--r-- 1 root root   339968 2012-06-29 14:44 db.data
> -rw-r--r-- 1 root root   196984 2012-06-29 14:44 db.redo
> -rw-r--r-- 1 root root        0 2012-06-26 16:40 lock
> {code}

--
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