Uploaded image for project: 'ActiveMQ Classic'
  1. ActiveMQ Classic
  2. AMQ-1885

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

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 5.1.0
    • 5.2.0
    • Broker
    • None
    • 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.

      Attachments

        Activity

          People

            gtully Gary Tully
            gtully Gary Tully
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: