[
https://issues.apache.org/activemq/browse/AMQ-2935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy updated AMQ-2935:
----------------------
Priority: Blocker (was: Major)
I have elevated this to 'Blocker' due to the fact that others are also
experiencing this, and that the general solution for everyone is to physically
delete files in order to continue - not an option in production.
The bug is consistently repeatable and is destructive in that files are left in
an unrecoverable state - The ability of ActiveMQ to recover from a crash is a
feature, so the the ability to recover from a simple restart is ultimately
critical.
> 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
> 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.
