[AMQ-6249] Slave node should try to get lock in small intervals to check JDBC connectivity

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Abandoned
• Affects Version/s: 5.11.1
• Component/s: JDBC

Environment

ServiceMix 5.4.1

• Patch Info: Patch Available
• Assignee: Unassigned
• Reporter: metatech
• Created: 14/Apr/16 14:59
• Updated: 13/Mar/22 14:16
• Resolved: 13/Mar/22 14:16

Description

In a JDBC master/slave configuration, the master node gets the lock in the database table ACTIVEMQ_LOCK and becomes active. The slave node tries to get the lock and waits indefinitely on the SQL query.
In case of a network device failure, the TCP connection to the DB server is abruptly removed, and no FIN nor RST is sent to the broker. This results into a slave node which never resumes from this network issue without manual restart of the broker.
The attached patch transforms the indefinite wait on the lock into a loop in small time intervals (defined by the "queryTimeout" variable). Also, it becomes possible to specify a TCP socket timeout at the JDBC driver level (for instance "oracle.jdbc.ReadTimeout" for Oracle) as an extra safety measure.
In the default case, the "queryTimeout=-1", which falls back to the indefinite wait.