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

Message can remain inflight after consumer side expiration acknowledgements

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 5.13.3
    • Fix Version/s: 5.14.0
    • Component/s: Broker
    • Labels:
      None

      Description

      If the client clock is slightly ahead of the brokers clock a message could be expired on the client but not considered expired on the broker.

      When the expiry ACK is sent to the broker it checks if the message is also considered expired on the broker side. If the broker clock is behind the client side clock the message could be considered not expired on the broker and not
      removed from the broker's dispatched list. This leaves the broker reporting a message inflight from the broker's perspective even though the message has been expired on the consumer(client) side

      The broker should treat the expired ACK as the authority on whether a message is expired and process it as such regardless of the broker side clock.

        Attachments

          Activity

            People

            • Assignee:
              gtully Gary Tully
              Reporter:
              tabish Timothy A. Bish
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: