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

Queue#MessageCount negative and messages stop flowing to AMQP consumer

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • AMQ 7.4.0.CR2
    • AMQ 7.1.0.GA, AMQ 7.2.0.GA, AMQ 7.2.1.GA, AMQ 7.2.2.GA
    • amq-online
    • Release Notes
    • +
    • Hide
      Previously, an AMQP client could send a disposition for a delivered message indicating that the client received the message but didn’t consume it. This behavior could cause the message count on the broker to have a negative value. This issue is now resolved.
      Show
      Previously, an AMQP client could send a disposition for a delivered message indicating that the client received the message but didn’t consume it. This behavior could cause the message count on the broker to have a negative value. This issue is now resolved.
    • Documented as Resolved Issue
    • Verified in a release
    • Hide

      It is possible to reset the MessageCount number to 0 via the JMX operation resetMessageCounter(), which is exposed for each broker destination.

      Show
      It is possible to reset the MessageCount number to 0 via the JMX operation resetMessageCounter(), which is exposed for each broker destination.

    Description

      As described by https://issues.apache.org/jira/browse/ARTEMIS-1982, we encountered a situation with Artemis 2.5.0 where the MessageCount for a queue went negative and messages stopped flowing to a AMQP Consumer. This defect has been seen once whilst performing an EnMasse performance test. The version of EnMasse under test used Artemis 2.5.0.

      This issue seems distinct from ENTMQBR-924.

      I have a heap dump collected from Artemis Broker if useful.

      Attachments

        Issue Links

          causes

          Bug - A problem that impairs or prevents the functions of the product. ENTMQMAAS-704 [#1442] : Pooled Queue reports negative message count after sustained load

          • 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

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-924 Negative Message Count and Delivering Count

          • 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

          Activity

            People

              rhn-support-jbertram Justin Bertram
              keithbwall Keith Wall
              Roman Vais Roman Vais
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: