Uploaded image for project: 'AMQ Broker'
  1. AMQ Broker
  2. ENTMQBR-411

[AMQP] Broker fails Lite transaction test

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Major Major
    • A-MQ 7.0.0.ER7
    • A-MQ 7.0.0.ER7
    • None
    • Release Notes
    • Hide
      When a message is enlisted in a transaction by having an accepted disposition but is not settled, and the transaction is rolled back by the client, the broker should treat that message as still being acquired by the receiver and not redeliver it again and the receiver should be able to consume, modify, reject or release the delivery on its own afterwards.

      It seems that the broker allows for a client to accept but not settle inside of a TX but if that TX is rolled back it appears that the message will later be redelivered even if they are immediately accepted in a new TX and that TX is committed.

      A resolution for this issue is under development.
      Show
      When a message is enlisted in a transaction by having an accepted disposition but is not settled, and the transaction is rolled back by the client, the broker should treat that message as still being acquired by the receiver and not redeliver it again and the receiver should be able to consume, modify, reject or release the delivery on its own afterwards. It seems that the broker allows for a client to accept but not settle inside of a TX but if that TX is rolled back it appears that the message will later be redelivered even if they are immediately accepted in a new TX and that TX is committed. A resolution for this issue is under development.

      This isn't a bug report unless transactions are supported. I had the setup to run Lite self tests against Artemis and hit this issue. Having generated the analysis (whether or not tx is supported) I need a place to store the facts, and this is it. The LiteTest-vs-Broker scoreboard shows:

      • A-MQ7 - test fail
      • QPIDD - test fail
      • Lite test broker - test pass

      All three brokers respond to transactions differently, with the most difference showing up in the Disposition sent to the client for a transacted message.

              rh-ee-ataylor Andy Taylor
              crolke@redhat.com Chuck Rolke (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: