Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 11084 invoked from network); 12 Sep 2007 06:45:00 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 12 Sep 2007 06:45:00 -0000 Received: (qmail 3923 invoked by uid 500); 12 Sep 2007 06:44:52 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 3902 invoked by uid 500); 12 Sep 2007 06:44:52 -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 3893 invoked by uid 99); 12 Sep 2007 06:44:52 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Sep 2007 23:44:52 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of pdvyuan@gmail.com designates 64.233.182.184 as permitted sender) Received: from [64.233.182.184] (HELO nf-out-0910.google.com) (64.233.182.184) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 Sep 2007 06:44:50 +0000 Received: by nf-out-0910.google.com with SMTP id b21so86153nfd for ; Tue, 11 Sep 2007 23:44:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type; bh=VRZOvOxn0Ny9WbJpUczpj3dMO2BzjTXVDKxjXhhZy3U=; b=HUZjLp06afr9mww9hvj8lQS3thzpDbV9a0Iemyz+plXcTy6XwG4pYd76yas1O0CamA0tsiSWzoiY0p22Y6SqifLEbsREfijfZxznpnjPuN493lE+o25ez8bcyltF6AO3JY006yRH5xppNP6YTsg8bHuokg0FbKA7wpwaAm3sDrc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type; b=AlNc7p3llfjsywBlVYMWieGbi0ZTZELiSE5SEmbcAOeuOn+PCOAgUuSEp7rxz8SXRnl1xoF5ORYtcKOyinZ+2ZBLNjaUDGCLpp48/aTX0CkZrEbD/34Kx6qnLJzW0TvXRKmVFeGjqb+Bshpn+EgEp1cKTBuDPSavQgfH5dmMu1I= Received: by 10.78.150.7 with SMTP id x7mr2986037hud.1189579468299; Tue, 11 Sep 2007 23:44:28 -0700 (PDT) Received: by 10.78.165.8 with HTTP; Tue, 11 Sep 2007 23:44:28 -0700 (PDT) Message-ID: <33f0307c0709112344w4cbb33dk35ee635d811bb145@mail.gmail.com> Date: Wed, 12 Sep 2007 14:44:28 +0800 From: "Dingwen Yuan" To: users@activemq.apache.org Subject: Master/Slave jdbc row lock can't be auto-released MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_21690_12688304.1189579468296" X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_21690_12688304.1189579468296 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi folks, We have tested master/slave configuration with pure jdbc persistence and the db used are mysql and postgres. When we plugged out the electric cable of the master machine, the row lock on the table ACTIVEMQ_LOCK cannot be released. So later neither of the machines can get the lock and become the master? Is the a known problem? Does any database support row lock auto release? Thanks Dingwen Yuan ------=_Part_21690_12688304.1189579468296--