Uploaded image for project: 'ActiveMQ Artemis'
  1. ActiveMQ Artemis
  2. ARTEMIS-2110

JDBC LeaseLocker repeated renew or renew after aquire can fail in error

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 2.6.3
    • Fix Version/s: 2.6.4, 2.7.0
    • Component/s: Broker
    • Labels:
      None

      Description

      There is an intermittent failure in:

      org.apache.activemq.artemis.core.server.impl.jdbc.JdbcLeaseLockTest#shouldRenewAcquiredLock

      (seems to block pr ci, and reproduced for me 20% of the time)

      if the db currentTime has not moved on, using the same lease time results in a failure. A renew immediately after acquiring the lock is a sensible pattern to verify the aquire. 

       

      The lock renew needs >= in place or > on the WHERE clause to allow an 'identity' lease to succeed.

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved: