Return-Path: 
 <dev-return-22848-apmail-activemq-dev-archive=activemq.apache.org@activemq.apache.org>
Delivered-To: apmail-activemq-dev-archive@www.apache.org
Received: (qmail 78791 invoked from network); 19 Oct 2010 10:20:08 -0000
Received: from unknown (HELO mail.apache.org) (140.211.11.3)
  by 140.211.11.9 with SMTP; 19 Oct 2010 10:20:08 -0000
Received: (qmail 91404 invoked by uid 500); 19 Oct 2010 10:20:08 -0000
Delivered-To: apmail-activemq-dev-archive@activemq.apache.org
Received: (qmail 91214 invoked by uid 500); 19 Oct 2010 10:20:05 -0000
Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@activemq.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@activemq.apache.org>
List-Post: <mailto:dev@activemq.apache.org>
List-Id: <dev.activemq.apache.org>
Reply-To: dev@activemq.apache.org
Delivered-To: mailing list dev@activemq.apache.org
Received: (qmail 91206 invoked by uid 99); 19 Oct 2010 10:20:04 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Oct 2010 10:20:04 +0000
X-ASF-Spam-Status: No, hits=-1998.7 required=10.0
	tests=ALL_TRUSTED,URI_HEX
X-Spam-Check-By: apache.org
Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Oct 2010 10:20:03 +0000
Received: from thor (localhost [127.0.0.1])
	by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o9JAJhmN027198
	for <dev@activemq.apache.org>; Tue, 19 Oct 2010 10:19:43 GMT
Message-ID: <22513320.60011287483583006.JavaMail.jira@thor>
Date: Tue, 19 Oct 2010 06:19:43 -0400 (EDT)
From: "John Fletcher (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Subject: [jira] Commented: (AMQ-2945) KahaDB corrupted when too many
 messages accumulate: EOFException
In-Reply-To: <15265724.33431285576600375.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: ae95407df07c98740808b2ef9da0087c


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

John Fletcher commented on AMQ-2945:
------------------------------------

I tried it and it's working well, it accumulated data for 72 hours without crashing. I think you can consider this fixed, thanks.

> KahaDB corrupted when too many messages accumulate: EOFException
> ----------------------------------------------------------------
>
>                 Key: AMQ-2945
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2945
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Message Store
>    Affects Versions: 5.4.0, 5.4.1
>         Environment: Windows XP, running as service.
>            Reporter: John Fletcher
>         Attachments: 5.4.0.log
>
>
> I am finding the KahaDB on a broker is becoming corrupted after a certain time of being disconnected (or perhaps rather, after a certain amount of messages are queued up). My config is extremely simple - originally 5.4.0 and now 5.4.1 on Windows with the default config, except adding a connection to a broker on an external machine with
> <networkConnectors>
>   <networkConnector uri="static:(tcp://machine1:61616,tcp://machine2:61616)"/>
> </networkConnectors>
> In this case the external machine/consumer is only on during business hours whereas the broker producing the messages is on 24/7. We're finding that generally the producer instance survives weeknights, during which it accumulates about 75,000 messages and then offloads them in the morning to
> the consumer instance, but not weekends. Last time it failed after about collecting about 160,000 messages.
> I get the excepton: ERROR | Failed to start ActiveMQ JMS Message Broker. Reason: java.io.EOFException: Chunk stream does not exist at page: 0 | org.apache.activemq.broker.BrokerService | WrapperSimpleAppMain - and plenty more, I'll attach the log.
> On 5.4.0 I found that only after deleting the file db.data was I able to restart the broker again. On one test run on 5.4.1 I'm finding that deleting db.data is not solving the problem.
> I noticed two other users described experiencing exactly the same problem:
> http://activemq.2283324.n4.nabble.com/Kaha-corruption-in-5-4-SNAPSHOT-td2366036.html
> To replicate the problem, I think it would probably suffice to start a broker with default config and let 300,000 messages accumulate without being consumed - I'm guessing the problem should occur before you get there. But perhaps you'll need to create a networkconnector as I have done and try the same thing. Will attach log...

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