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

[jms] client-ack consumers don't increment remote delivery count on closure after fresh recover

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 2.6.0.B1
    • 2.5.0.GA
    • qpid-jms
    • None
    • +
    • Hide

      test project attached

      broker example address-setting:

               <address-setting match="foo">
             <redelivery-delay-multiplier>2</redelivery-delay-multiplier>
             <redelivery-delay>2000</redelivery-delay>
             <max-redelivery-delay>4000</max-redelivery-delay>
             <dead-letter-address>foo.dlq</dead-letter-address>
             <max-delivery-attempts>2</max-delivery-attempts>
         </address-setting>
      Show
      test project attached broker example address-setting: <address-setting match= "foo" > <redelivery-delay-multiplier>2</redelivery-delay-multiplier> <redelivery-delay>2000</redelivery-delay> <max-redelivery-delay>4000</max-redelivery-delay> <dead-letter-address>foo.dlq</dead-letter-address> <max-delivery-attempts>2</max-delivery-attempts> </address-setting>
    • Wawona

    Description

      For AMQP clients, increment the delivery count for the following scenario:

      1. a message is delivered to application
      2. session.recover() is called
      3. the consumer is closed

      This is relevant to non-transacted AMQP consumers; currently when a Camel client throws an exception in the following route, the re-delivery counter is not incremented and the message will continue being re-delivered forever:

      from("amqp-component:mytest.queueName?cacheLevelName=CACHE_NONE&acknowledgementModeName=CLIENT_ACKNOWLEDGE")
      .throwException(new Exception("FORCED EXCEPTION"));

      Client Ack is a requirement here to avoid setting up a separate coordinator link for local transactions.

      Attachments

        Issue Links

          is related to

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. ENTMQCL-1953 [jms] client-ack with Camel CACHE_AUTO broker-side redelivery

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed
          links to

          Web Link https://issues.apache.org/jira/browse/QPIDJMS-484

          Activity

            People

              gemmellr Robbie Gemmell
              rhn-support-shiggs Stephen Higgs
              Jiri Daněk Jiri Daněk
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: