Mailing-List: contact issues-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Mon, 20 Nov 2017 14:13:00 +0000 (UTC)
From: "Timothy Bish (JIRA)" <jira@apache.org>
To: issues@activemq.apache.org
Message-ID: <JIRA.13119567.1511163101000.280440.1511187180727@Atlassian.JIRA>
In-Reply-To: <JIRA.13119567.1511163101000@Atlassian.JIRA>
References: <JIRA.13119567.1511163101000@Atlassian.JIRA> <JIRA.13119567.1511163101229@jira-lw-us.apache.org>
Subject: [jira] [Closed] (AMQ-6865) JDBC Master/Slave: Master did not leave
 lock when the master loose database connection.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 20 Nov 2017 14:13:05 -0000


     [ https://issues.apache.org/jira/browse/AMQ-6865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timothy Bish closed AMQ-6865.
-----------------------------
    Resolution: Invalid

Issue with other spins of ActiveMQ not released by the AcitveMQ community require that you seek support from the entity that released them, in this case you should contact Red Hat and log an issue using your support contract if you have one.  

> JDBC Master/Slave: Master did not leave lock when the master loose database connection.
> ---------------------------------------------------------------------------------------
>
>                 Key: AMQ-6865
>                 URL: https://issues.apache.org/jira/browse/AMQ-6865
>             Project: ActiveMQ
>          Issue Type: Bug
>            Reporter: Pranjal Bathia
>
> We have JBoss AMQ instance of  jboss-a-mq-6.3.0.redhat-187, and we use JDBC for master/slave configuration. 
> As per our observation, during networking disruption for connecting to the database, a broker was unable to recover cleanly. 
> In hawtio, both master/slave was showing as master, and ActiveMQ tab with amq connection was available on both broker and which resulted in a situation where one app was sending messages to broker01 (which was acting as producer) and all consumers were connected to broker02. 
> We have below setting :
> <persistenceAdapter>
>              <jdbcPersistenceAdapter dataSource="#mysql-ds" lockKeepAlivePeriod="5000">
>                 <locker>
>                    <lease-database-locker lockAcquireSleepInterval="10000"/>
>                 </locker>
>              </jdbcPersistenceAdapter>
>   </persistenceAdapter>
> We had seen this issue in production, we did not get a chance to look at an activemq_lock table.


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)