activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Tully (Closed) (JIRA)" <>
Subject [jira] [Closed] (AMQ-1958) JDBC master/slave deadlock when connection is lost
Date Tue, 17 Apr 2012 15:56:17 GMT


Gary Tully closed AMQ-1958.

       Resolution: Duplicate
    Fix Version/s:     (was: NEEDS_REVIEWED)
> JDBC master/slave deadlock when connection is lost
> --------------------------------------------------
>                 Key: AMQ-1958
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker, Message Store
>    Affects Versions: 4.1.2, 5.0.0, 5.1.0, 5.2.0
>         Environment: oracle 10, mysql 5
>            Reporter: Guy Veraghtert
>             Fix For: 5.6.0
> In a pure JDBC failover scenario with one master and one slave: when the master loses
its network connection to the database, the lock in the database will not be released. As
such the slave will not know that the master isn't able to perform its work and it will continue
to attempt to acquire a lock (which will never be released), when the master is restarted
(after its connection is restored), it will become slave too, ending up with two slaves.
> This behavior was encountered on Oracle 10 and Mysql 5.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message