Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Message-ID: <18611717.46011286303691621.JavaMail.jira@thor>
Date: Tue, 5 Oct 2010 14:34:51 -0400 (EDT)
From: "Swapnonil Mukherjee (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Subject: [jira] Commented: (AMQ-2935) java.io.EOFException: Chunk stream
 does not exist at page on broker start
In-Reply-To: <32534813.29141285245880372.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


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

Swapnonil Mukherjee commented on AMQ-2935:
------------------------------------------

Hi Gary,

I can indeed confirm that in our case the problem started only after someone killed the activemq process using kill -9. As I reported earlier, when I deleted everything under localhost/scheduler folder and restarted activemq it started cleanly.

With regards to your suggestion of testing 5.5 Snapshot; Are you saying that with 5.5 activemq can recover correctly from these kill -9 type shutdowns and we won't see this "Chunk Stream" errors? 

> java.io.EOFException: Chunk stream does not exist at page on broker start
> -------------------------------------------------------------------------
>
>                 Key: AMQ-2935
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2935
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.4.0, 5.4.1, 5.5.0
>         Environment: Win7 32bit, JDK 1.6_20
>            Reporter: Andy
>            Assignee: Gary Tully
>            Priority: Blocker
>         Attachments: activemq-data.zip, activemq.xml, stacktraces.txt
>
>
> I am seeing this regularly upon restarts in all versions from 5.4.x - I cannot downgrade due to breaking issues in previous versions.
> The broker was shutdown cleanly with no logged issues.
> Deleting the activemq-data directory seems to be the only recovery solution (which is not an option in production)
> 2010-09-23 13:54:30,997 [Starting ActiveMQ Broker] ERROR org.apache.activemq.broker.BrokerService - Failed to start ActiveMQ JMS Message Broker. Reason: java.io.EOFException: Chunk stream does not exist at page: 0
> java.io.EOFException: Chunk stream does not exist at page: 0
> 	at org.apache.kahadb.page.Transaction$2.readPage(Transaction.java:454)
> 	at org.apache.kahadb.page.Transaction$2.<init>(Transaction.java:431)
> 	at org.apache.kahadb.page.Transaction.openInputStream(Transaction.java:428)
> 	at org.apache.kahadb.page.Transaction.load(Transaction.java:404)
> 	at org.apache.kahadb.page.Transaction.load(Transaction.java:361)
> 	at org.apache.activemq.broker.scheduler.JobSchedulerStore$3.execute(JobSchedulerStore.java:250)
> 	at org.apache.kahadb.page.Transaction.execute(Transaction.java:728)
> 	at org.apache.activemq.broker.scheduler.JobSchedulerStore.doStart(JobSchedulerStore.java:239)
> 	at org.apache.activemq.util.ServiceSupport.start(ServiceSupport.java:53)
> 	at org.apache.activemq.broker.scheduler.SchedulerBroker.getStore(SchedulerBroker.java:198)
> 	at org.apache.activemq.broker.scheduler.SchedulerBroker.getInternalScheduler(SchedulerBroker.java:185)
> 	at org.apache.activemq.broker.scheduler.SchedulerBroker.start(SchedulerBroker.java:85)
> 	at org.apache.activemq.broker.BrokerFilter.start(BrokerFilter.java:157)
> 	at org.apache.activemq.broker.BrokerFilter.start(BrokerFilter.java:157)
> 	at org.apache.activemq.broker.TransactionBroker.start(TransactionBroker.java:112)
> 	at org.apache.activemq.broker.BrokerService$3.start(BrokerService.java:1786)
> 	at org.apache.activemq.broker.BrokerService.start(BrokerService.java:496)
> 	at org.apache.activemq.ra.ActiveMQResourceAdapter$1.run(ActiveMQResourceAdapter.java:85)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.