Return-Path: X-Original-To: apmail-activemq-users-archive@www.apache.org Delivered-To: apmail-activemq-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1BEE3DA32 for ; Thu, 15 Nov 2012 11:23:50 +0000 (UTC) Received: (qmail 87792 invoked by uid 500); 15 Nov 2012 11:23:49 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 87360 invoked by uid 500); 15 Nov 2012 11:23:48 -0000 Mailing-List: contact users-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@activemq.apache.org Delivered-To: mailing list users@activemq.apache.org Received: (qmail 87295 invoked by uid 99); 15 Nov 2012 11:23:45 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 Nov 2012 11:23:45 +0000 X-ASF-Spam-Status: No, hits=2.0 required=5.0 tests=SPF_NEUTRAL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: 216.139.250.139 is neither permitted nor denied by domain of torbjornsk@gmail.com) Received: from [216.139.250.139] (HELO joe.nabble.com) (216.139.250.139) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 Nov 2012 11:23:39 +0000 Received: from [192.168.236.139] (helo=joe.nabble.com) by joe.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1TYxXS-0001dw-Dv for users@activemq.apache.org; Thu, 15 Nov 2012 03:23:18 -0800 Date: Thu, 15 Nov 2012 03:23:18 -0800 (PST) From: Tobb To: users@activemq.apache.org Message-ID: <1352978598424-4659388.post@n4.nabble.com> Subject: JournaledPersistenceAdapter error prone? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org We have AMQ 5.6.0 set up using a journaledPersistenceAdapter. In the last few days we've experienced numerous problems relating to this. It seems that when AMQ is shut down, it dumps its state into the journal files, but when we try to start the AMQ service again, it fails due to: To solve this, we have to remove the journal files from the disk and restart. Since this is in a production environment, I'm not really happy having to do this, I fear that data will be lost. We used journaled persistence with AMQ 5.3.0 previously, and never had this problem. Is this a known issue? -Tobb -- View this message in context: http://activemq.2283324.n4.nabble.com/JournaledPersistenceAdapter-error-prone-tp4659388.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.