Uploaded image for project: 'AMQ Clients'
  1. AMQ Clients
  2. ENTMQCL-484

[jms] Race on connection start and message dispatch can deliver messages in wrong order

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Critical Critical
    • 1.1.0-GA-B2
    • 1.1.0-beta-2
    • qpid-jms
    • None
    • Release Notes
    • Hide
       - Cause: A race between handling of previously prefetched and newly-arriving messages for a consumer when Connection#start() is called after creation of the consumer.
       - Consequence: Messages could be received in an unexpected order due to some leap-frogging others.
       - Fix: An intermediate data structure was removed to prevent the race and ensure the correct delivery order in this situation.
       - Result: Messages are received in the expected order when when Connection#start() is called after creation of the consumer.
      Show
       - Cause: A race between handling of previously prefetched and newly-arriving messages for a consumer when Connection#start() is called after creation of the consumer.  - Consequence: Messages could be received in an unexpected order due to some leap-frogging others.  - Fix: An intermediate data structure was removed to prevent the race and ensure the correct delivery order in this situation.  - Result: Messages are received in the expected order when when Connection#start() is called after creation of the consumer.
    • Documented as Resolved Issue

      If a connection is started in which consumer have been created and messages are incoming a call to start can end in a race where on incoming message can jump the line and be delivered ahead of previously queued messages.

              jross@redhat.com Justin Ross
              gemmellr Robbie Gemmell
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: