You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2011/08/23 21:38:28 UTC

[jira] [Closed] (AMQ-3221) EOFException: Chunk stream does not exist at page: 0 Re-appears

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

Timothy Bish closed AMQ-3221.
-----------------------------

    Resolution: Duplicate

Several recent fixes have gone into the code for issues that were similar to this.  No test case given and no logs so hard to verify for sure if your case is fixed.  Recommend that you try the latest SNAPSHOT build and see if you experience anything like this.  Reopen if the problem appears again.

> EOFException: Chunk stream does not exist at page: 0 Re-appears
> ---------------------------------------------------------------
>
>                 Key: AMQ-3221
>                 URL: https://issues.apache.org/jira/browse/AMQ-3221
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.4.2
>         Environment: Using activemq 0.2.1 plug in in Grails 1.3.4 environment under Ubuntu 10.04
>            Reporter: Trevor Allen
>
> Encountered this problem:
> 2011-03-16 10:52:23,462 [main] ERROR 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
> with ActiveMQ 5.4.1 and activemq 0.1 plug in. Found AMQ 2935 describing this issue and upgraded my environment to that shown in the issue description. Did this during a running Grails app and the problem seemed to go away. However, booting up this morning from a cold start it has re-appeared.
> I'm relatively new to this type of environment - is there something else I should have done? Stacktrace etc available if needed.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira