activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andy (JIRA)" <>
Subject [jira] Commented: (AMQ-2935) Chunk stream does not exist at page on broker start
Date Tue, 05 Oct 2010 09:39:51 GMT


Andy commented on AMQ-2935:


Only using "schedulerSupport=false" does NOT resolve this issue. The problem is specifically
a KahaDB problem (the default persistence store is KahaDB).

Swapping out the persistence store is currently the only option. If you need 'any' persistence
then I would suggest the jdbcPersistenceAdapter (the default uses a Derby Database, but many
can be used).
This is substantially slower than KahaDB, but not enough to worry about if you are only pushing
say several thousand messages a minute (you'd have to run your own tests). I am in fact happy
enough with the performance that I am likely to stick with it for stabilities sake even if
this issue is resolved.

<broker xmlns=""

      <jdbcPersistenceAdapter dataDirectory="activemq-data/jdbc"/>


Note: If schedulerSupport is enabled then the error will still persist (excuse the pun) due
to the fact that the scheduler uses KahaDB irrelevant of the persistenceAdapter - So if you
want scheduler support then there is currently no option (unless someone knows how to configure
the scheduler to use another store?).


I should have mentioned that my configuration is for an OpenEJB RA, whereby the RA is responsible
for starting and stopping ActiveMQ (which is does, and still produces a corrupt KahaDB) -
The default OpenEJB RA config uses a memory store, but I require persistence for my project.
A standalone application (basically as Krzysztof writes) which loops through start/stop will
still produce the same stacktrace virtually every time.

> Chunk stream does not exist at page on broker start
> -------------------------------------------------------------------------
>                 Key: AMQ-2935
>                 URL:
>             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.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
- Failed to start ActiveMQ JMS Message Broker. Reason: Chunk stream
does not exist at page: 0
> Chunk stream does not exist at page: 0
> 	at$2.readPage(
> 	at$2.<init>(
> 	at
> 	at
> 	at
> 	at$3.execute(
> 	at
> 	at
> 	at org.apache.activemq.util.ServiceSupport.start(
> 	at
> 	at
> 	at
> 	at
> 	at
> 	at
> 	at$3.start(
> 	at
> 	at org.apache.activemq.ra.ActiveMQResourceAdapter$

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

View raw message