ActiveMQ
  1. ActiveMQ
  2. AMQ-1885

The jdbc lockKeepAlive thread should be started only if current broker instance successfully started and became a master

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 5.1.0
    • Fix Version/s: 5.2.0
    • Component/s: Broker
    • Labels:
      None
    • Environment:

      jdbc persistence adapter with master/slave

      Description

      using jdbc persistence with master/slave sharing the database. If the db dies, the master dies when it sees its lock expire. unfortunately the slave also has a lockKeepalive thread that detects the db failure, even if it does not have the lock.
      The lockKeepAlive thread should be used once a lock has been acquired. in this way, the slave can remain trying to acquire the lock and eventually succeed and promote its self to master when the db comes back up.

        Activity

        Hide
        Gary Tully added a comment -

        fixed in revision 685988.
        Added two jdbc master slave tests cases, normal failover after master dies and failover after temporary db outage.

        Show
        Gary Tully added a comment - fixed in revision 685988. Added two jdbc master slave tests cases, normal failover after master dies and failover after temporary db outage.

          People

          • Assignee:
            Gary Tully
            Reporter:
            Gary Tully
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development