[AMQ-1958] JDBC master/slave deadlock when connection is lost

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 4.1.2, 5.0.0, 5.1.0, 5.2.0
• Fix Version/s: 5.6.0
• Component/s: Broker, Message Store

Environment

oracle 10, mysql 5

• Assignee: Unassigned
• Reporter: Guy Veraghtert
• Created: 29/Sep/08 14:10
• Updated: 17/Apr/12 15:56
• Resolved: 17/Apr/12 15:56

Description

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.

Issue Links

• relates to: AMQ-3654 JDBC Master/Slave : Slave cannot acquire lock when the master loose database connection.