Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: error (athena.apache.org: encountered temporary error during SPF
 processing of domain of victorhdamian@gmail.com)
Date: Tue, 11 Jun 2013 10:24:34 -0700 (PDT)
From: victorhdamian <victorhdamian@gmail.com>
To: users@activemq.apache.org
Message-ID: <1370971474711-4668099.post@n4.nabble.com>
In-Reply-To: <1311679528547-3695392.post@n4.nabble.com>
References: <AANLkTim_NPyHV-gCzcB8pH2m0eyso2vm25p-_byNWHFP@mail.gmail.com>
 <AANLkTi=AjMsTOKT-RidXhtiHoKfGzz7NAgVVo0NveQF+@mail.gmail.com>
 <AANLkTin=bEzOEeCezsXBHpvxgHRArqxdLdsCcTrKBP8N@mail.gmail.com>
 <1311679528547-3695392.post@n4.nabble.com>
Subject: Re: KahaDB corruption
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Try this:
ActiveMQ v5.5.1 Corrupt data log found recovery:

Symptom:
The ActiveMQ slave process died and will not restarted.

Root Cause:
Corrupt data log found

Root Cause verification:
Search the affected ActiveMQ log file for the following entries in sequence:
Corrupt journal records found
Failed to discard data file
Failed to start ActiveMQ JMS Message Broker
shutting down

Recovery:
Shutdown the ActiveMQ master instance.
Rename the Kaha db storage file
Restart the ActiveMQ Master and Slave instances

Note: the journal data affected by the corruption will be lost. The affected
journal data will need to be identify and resent to the ActiveMQ appropriate
queue.


--
View this message in context: http://activemq.2283324.n4.nabble.com/KahaDB-corruption-tp3321382p4668099.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.