[
https://issues.apache.org/jira/browse/AMQ-3654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13193863#comment-13193863
]
metatech commented on AMQ-3654:
-------------------------------
If the database connection is abruptly lost (no TCP FIN nor RST), for instance
when the network cable is unplugged, the DB client application cannot release
the lock anymore.
The DB server itself needs to detect the dead connection.
On Oracle the parameter "SQLNET.EXPIRE_TIME" can be used.
> JDBC Master/Slave : Slave cannot acquire lock when the master loose database
> connection.
> ----------------------------------------------------------------------------------------
>
> Key: AMQ-3654
> URL: https://issues.apache.org/jira/browse/AMQ-3654
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.5.0
> Environment: Unix/Redhat 5.6
> ActiveMQ 5.5.0
> Oracle 10G
> Reporter: Richard Martin
> Priority: Critical
> Fix For: 5.6.0
>
>
> Our configuration is JDBC Master/Slave with one master and one slave. When
> the master is started, he acquire the database lock.
> Then when the slave is started, he wait to acquire the database lock. When
> the master loose the network connection to the database, the lock in the
> database is not removed and the slave connot acquire the database lock. In
> this situation, the master is unable to respond to client (due to network
> failure)
> and the slave is not started because he can't acquire the database lock.
> When the master is killed, the slave can't acquire the database lock too.
> After the network connection is restored, when the master starts, it cannot
> acquire lock to the database (because the lod lock is always present) so now,
> we have two slaves and no master.
> Please, refer to this issue which is the same problem : AMQ-1958
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
