From users-return-10938-apmail-activemq-users-archive=activemq.apache.org@activemq.apache.org Wed Oct 10 16:13:16 2007 Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 21962 invoked from network); 10 Oct 2007 16:13:14 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 10 Oct 2007 16:13:14 -0000 Received: (qmail 55317 invoked by uid 500); 10 Oct 2007 15:42:21 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 55298 invoked by uid 500); 10 Oct 2007 15:42:21 -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 55287 invoked by uid 99); 10 Oct 2007 15:42:21 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Oct 2007 08:42:21 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Oct 2007 15:42:24 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1IfdhD-0004QY-Dj for users@activemq.apache.org; Wed, 10 Oct 2007 08:42:03 -0700 Message-ID: <13138495.post@talk.nabble.com> Date: Wed, 10 Oct 2007 08:42:03 -0700 (PDT) From: naql To: users@activemq.apache.org Subject: Yes, and it's an urgent problem [was Re: lock on Oracle activemq_lock table] In-Reply-To: <13064911.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: andrew_hart@harcourt.com References: <13064911.post@talk.nabble.com> X-Virus-Checked: Checked by ClamAV on apache.org kmoore4now wrote: > > I'm using the journaled JDBC approach to message persistence, with Oracle. > It seems to work well most of the time. However, I'm finding that even > after a normal shutdown a lock occasionally appears to be held on the > activemq_lock table. This prevents ActiveMQ from starting up again on the > next attempt. > > Has anyone else seen this? Is there a way to avoid it? > Yes. I'm pretty sure the problem you're describing here is the same one that I'm running into. I previously posted regarding this on Oct 2nd as "ActiveMQ installed as NT service takes a long, long time to restart". I thought it might be related to the servicewrapper, but it happens just running it from the prompt whenever I use Oracle jdbc persistence. I see these messages in the log: 2007-10-02 17:44:50,232 [erSimpleAppMain] INFO DefaultDatabaseLocker - Attempting to acquire the exclusive lock to become the Master broker 2007-10-02 19:42:06,568 [erSimpleAppMain] INFO DefaultDatabaseLocker - Becoming the master on dataSource: org.apache.commons.dbcp.BasicDataSource@1972e So, as you can see, in this example, it took 2 hours for ActiveMQ to start up. This doesn't happen when I fall back on the default persistence db, comment out the Oracle datasource. This is a big deal to us and, along with the other issue I'm about to post about, is a serious showstopper. -- View this message in context: http://www.nabble.com/lock-on-Oracle-activemq_lock-table-tf4576911s2354.html#a13138495 Sent from the ActiveMQ - User mailing list archive at Nabble.com.