From dev-return-31808-apmail-activemq-dev-archive=activemq.apache.org@activemq.apache.org Wed Jun 13 20:51:43 2012 Return-Path: X-Original-To: apmail-activemq-dev-archive@www.apache.org Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 912819657 for ; Wed, 13 Jun 2012 20:51:43 +0000 (UTC) Received: (qmail 70963 invoked by uid 500); 13 Jun 2012 20:51:43 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 70762 invoked by uid 500); 13 Jun 2012 20:51:43 -0000 Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list dev@activemq.apache.org Received: (qmail 70724 invoked by uid 99); 13 Jun 2012 20:51:43 -0000 Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Jun 2012 20:51:43 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id E849214001F for ; Wed, 13 Jun 2012 20:51:42 +0000 (UTC) Date: Wed, 13 Jun 2012 20:51:42 +0000 (UTC) From: "Gary Tully (JIRA)" To: dev@activemq.apache.org Message-ID: <419318764.13652.1339620702953.JavaMail.jiratomcat@issues-vm> In-Reply-To: <775745807.14851.1325862759810.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Assigned] (AMQ-3654) JDBC Master/Slave : Slave cannot acquire lock when the master loose database connection. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AMQ-3654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully reassigned AMQ-3654: ------------------------------- Assignee: Gary Tully > JDBC Master/Slave : Slave cannot acquire lock when the master loose database connection. > ---------------------------------------------------------------------------------------- > > Key: AMQ-3654 > URL: https://issues.apache.org/jira/browse/AMQ-3654 > Project: ActiveMQ > Issue Type: Bug > Affects Versions: 5.5.0 > Environment: Unix/Redhat 5.6 > ActiveMQ 5.5.0 > Oracle 10G > Reporter: Richard Martin > Assignee: Gary Tully > Priority: Critical > Fix For: 5.7.0 > > > Our configuration is JDBC Master/Slave with one master and one slave. When the master is started, he acquire the database lock. > Then when the slave is started, he wait to acquire the database lock. When the master loose the network connection to the database, the lock in the database is not removed and the slave connot acquire the database lock. In this situation, the master is unable to respond to client (due to network failure) > and the slave is not started because he can't acquire the database lock. > When the master is killed, the slave can't acquire the database lock too. After the network connection is restored, when the master starts, it cannot > acquire lock to the database (because the lod lock is always present) so now, we have two slaves and no master. > Please, refer to this issue which is the same problem : AMQ-1958 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira