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

Expiring of AMQP messages does not work

    XMLWordPrintable

Details

    • Hide

      1) Create a queue
      2) Send a message via AMQP protocol with defined TTL
      3) Wait TTL + few more seconds, messages should move to ExpiryQueue
      4) Read messages from ExpiryQueue and verify no message with ttl is in the original queue

      QE test: JAMQMsgPatternsAac111Tests/test_dead_letter_queue_with_expired_messages

      Show
      1) Create a queue 2) Send a message via AMQP protocol with defined TTL 3) Wait TTL + few more seconds, messages should move to ExpiryQueue 4) Read messages from ExpiryQueue and verify no message with ttl is in the original queue QE test: JAMQMsgPatternsAac111Tests/test_dead_letter_queue_with_expired_messages

    Description

      AMQP Messages having expire time (time to live) are sent to the queue and they won't expire and move to "default" ExpiryQueue.
      Openwire messages work properly in ER17. Seems like an issue with AMQP protocol only. clebert this might be related to your work I guess.

      In ER16, it works as expected. This is a regression.

      Attachments

        Issue Links

          is duplicated by

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-579 Broker fails to move expired messages sent with qpid-jms to expiry queue

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed
          is related to

          Bug - A problem that impairs or prevents the functions of the product. ENTMQCL-497 [python] Absolute expiry value seems to be by default 0 instead of None

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          relates to

          ARTEMIS-1090 Loading...

          Activity

            People

              csuconic@redhat.com Clebert Suconic
              mtoth@redhat.com Michal Toth
              Michal Toth Michal Toth
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: