Qpid
  1. Qpid
  2. QPID-3642

Implement Dead Letter Queue functionality

    Details

    • Type: New Feature New Feature
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 0.15
    • Component/s: Java Broker, Java Client
    • Labels:
      None

      Description

      Implement functionality to move messages into Dead Letter Queue on reaching Max Delivery Count limit.

      The Maximum Delivery Count is a property of a queue. If the client application is unable to process a message more than a specified number of times, the then the broker either moves the message to the specified DLQ, or it is dropped (producing an operation log message).

      If the application is unable to process a message it must call either Session#recover() or Session#rollback() (depending on transactionality) on the Session in use. If during recovery the broker discovers that a message has been seen (at least) the maximum number of times then it will move the message to the DLQ or drop the message, depending on how the queue is configured.

      This feature can be enabled for a queue either through the XML configuration for the broker, or when declaring the queue using JMX. It is also necessary to enable a setting on the client. The feature is available for both synchronous consumers (i.e. those using MessageConsumer#receive()) and asynchronous consumers (i.e. those implementing MessageListener#onMessage) using all JMS delivery modes.

      When enabled for a given queue, the DLQ feature causes generation of a Dead Letter Exchange and a Dead Letter Queue, named according to the convention <queue_name>_DLE and <queue_name>_DLQ. If the client indicates it no longer wishes the receive the message (by means of the Max Delivery Count feature) then the message is routed through the dead letter exchange onto the DLQ and removed from the original queue.

        Issue Links

          Activity

          Hide
          Alex Rudyy added a comment -

          Keith, could you please review and commit the patch attached?

          Show
          Alex Rudyy added a comment - Keith, could you please review and commit the patch attached?
          Hide
          Keith Wall added a comment -

          Hi Alex

          Couple of comments:

          1) Can you extract the separate bug fix we discussed into a separate Jira/patch?
          2) AMQBrokerManagerMBean#createNewQueue surely the old method should call the new override, and avaoid duplicating the method.
          3) AMQConnection.java could you document that rejectBehaviour member only applies to 0-8..0-9-1.

          Thanks, Keith.

          Show
          Keith Wall added a comment - Hi Alex Couple of comments: 1) Can you extract the separate bug fix we discussed into a separate Jira/patch? 2) AMQBrokerManagerMBean#createNewQueue surely the old method should call the new override, and avaoid duplicating the method. 3) AMQConnection.java could you document that rejectBehaviour member only applies to 0-8..0-9-1. Thanks, Keith.
          Hide
          Alex Rudyy added a comment -

          Keith,

          > 1) Can you extract the separate bug fix we discussed into a separate Jira/patch?

          I extracted changes into 2 patches.
          The first patch adds DLQ & max delivery count functionality for 0-8/0-9/0-9-1 paths.
          The second patch adds DLQ & max delivery count functionality for 0-10 paths.
          Also, in second patch I fixed issue with setting of re-delivery flag for pre-fetched messages(QPID-3640).

          > 2) AMQBrokerManagerMBean#createNewQueue surely the old method should call the new override, and avoid duplicating the method.

          Fixed.

          > 3) AMQConnection.java could you document that rejectBehaviour member only applies to 0-8..0-9-1.

          I moved getRejectBehaviour functionality from AMQConnection into BasicMessageConsumer_0_8 as it is the place where it is needed.
          However, I could not moved AMQDestinaton#getRejectBehaviour into BasicMessageConsumer, so, I added more commentaries about "rejectbehaviour" option in AMQDestinaton.

          Show
          Alex Rudyy added a comment - Keith, > 1) Can you extract the separate bug fix we discussed into a separate Jira/patch? I extracted changes into 2 patches. The first patch adds DLQ & max delivery count functionality for 0-8/0-9/0-9-1 paths. The second patch adds DLQ & max delivery count functionality for 0-10 paths. Also, in second patch I fixed issue with setting of re-delivery flag for pre-fetched messages( QPID-3640 ). > 2) AMQBrokerManagerMBean#createNewQueue surely the old method should call the new override, and avoid duplicating the method. Fixed. > 3) AMQConnection.java could you document that rejectBehaviour member only applies to 0-8..0-9-1. I moved getRejectBehaviour functionality from AMQConnection into BasicMessageConsumer_0_8 as it is the place where it is needed. However, I could not moved AMQDestinaton#getRejectBehaviour into BasicMessageConsumer, so, I added more commentaries about "rejectbehaviour" option in AMQDestinaton.
          Hide
          Alex Rudyy added a comment -

          Updated patches to fix JMX API version and docs.
          Refactored client to store pre-fetched message tags in a separate queue.

          Show
          Alex Rudyy added a comment - Updated patches to fix JMX API version and docs. Refactored client to store pre-fetched message tags in a separate queue.
          Hide
          Keith Wall added a comment - - edited

          Hi Alex/Andy

          My only comment is that AMQBrokerManagerMBean#createNewQueue has been changed to chain tyhe AMQException to the JMException. It is likely this will cause a unmarshall exception on the client as the client wont have the class. No other comments.

          cheers Keith

          Show
          Keith Wall added a comment - - edited Hi Alex/Andy My only comment is that AMQBrokerManagerMBean#createNewQueue has been changed to chain tyhe AMQException to the JMException. It is likely this will cause a unmarshall exception on the client as the client wont have the class. No other comments. cheers Keith
          Hide
          Alex Rudyy added a comment -

          Keith,

          I changed AMQBrokerManagerMBean#createNewQueue and updated patch.

          Show
          Alex Rudyy added a comment - Keith, I changed AMQBrokerManagerMBean#createNewQueue and updated patch.
          Hide
          Keith Wall added a comment -

          Patches applied.

          Show
          Keith Wall added a comment - Patches applied.
          Hide
          Keith Wall added a comment -

          As discussed, causing a regression failure against the Python test suite:

          https://builds.apache.org/view/M-R/view/Qpid/job/Qpid-Python-Java-Test/35/

          • qpid.tests.messaging.endpoints.ReceiverTests.testAtMostOnce
          • qpid.tests.messaging.endpoints.ReceiverTests.testUnreliable
          Show
          Keith Wall added a comment - As discussed, causing a regression failure against the Python test suite: https://builds.apache.org/view/M-R/view/Qpid/job/Qpid-Python-Java-Test/35/ qpid.tests.messaging.endpoints.ReceiverTests.testAtMostOnce qpid.tests.messaging.endpoints.ReceiverTests.testUnreliable
          Hide
          Andrew MacBean added a comment -

          Regression caused by our use of the redelivered flag when in ServerSession.onClose we call release on the subscriptions. Fixed this and changed the logic in subscription release method to handle correctly. Also added equivalent Java test for this case.

          Subsequent patch attached.

          Show
          Andrew MacBean added a comment - Regression caused by our use of the redelivered flag when in ServerSession.onClose we call release on the subscriptions. Fixed this and changed the logic in subscription release method to handle correctly. Also added equivalent Java test for this case. Subsequent patch attached.
          Hide
          Keith Wall added a comment -

          Patch applied.

          Show
          Keith Wall added a comment - Patch applied.

            People

            • Assignee:
              Keith Wall
              Reporter:
              Alex Rudyy
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development