activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rohan Mars (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-6865) JDBC Master/Slave: Master did not leave lock when the master loose database connection.
Date Wed, 28 Mar 2018 21:02:00 GMT

    [ https://issues.apache.org/jira/browse/AMQ-6865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16418098#comment-16418098
] 

Rohan Mars commented on AMQ-6865:
---------------------------------

The exception handler approach is additionally documented using the inbuilt syntax in the
Fuse AMQ docs:

[https://access.redhat.com/documentation/en-us/red_hat_jboss_a-mq/6.2/html/configuring_broker_persistence/mqpersiststorelock#MQLeaseDatabaseLocker]

 

> 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
>            Priority: Major
>
> 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
(v7.6.3#76005)

Mime
View raw message