ActiveMQ
  1. ActiveMQ
  2. AMQ-2186

Number of messages when browsing queue is different to "Number Of Pending Messages" in queue list

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: 5.2.0
    • Fix Version/s: 5.3.0
    • Component/s: Message Store
    • Labels:
      None
    • Environment:

      CentOS 5.2 64bit

      Description

      1. The Queues list displays a number, "Number Of Pending Messages" for like 1000.
      2. When clicking on that queue, the number of message (total of all rows) is smaller than 1000.

      Actually the #2 always displays a very small number of messages which is not more than 100 although the number on the list keep increasing to like forever.

      The problem doesn't happen when ActiveMQ starts but after one to a few hours instead. At the moment the only way to resolve this at our end is to restart the AMQ.

        Activity

        Loc Truong created issue -
        Loc Truong made changes -
        Field Original Value New Value
        Regression [Regression]
        Component/s Message Store [ 11080 ]
        Description When you "purge" queue from web admin console, it zeroes queue message
        counter. But if you have an active consumer at that time which
        pre-fetched messages than your consumer will keep sending ack as it
        process messages from its buffer. ActiveMQ will keep decrement counter
        upon receiving each ack. So when consumer is done queue will show
        MINUS<consumer buffer size>.

        1. The Queues list displays a number, "Number Of Pending Messages" for like 1000.
        2. When clicking on that queue, the number of message (total of all rows) is smaller than 1000.

        Actually the #2 always displays a very small number of messages which is not more than 100 although the number on the list keep increasing to like forever.

        The problem doesn't happen when ActiveMQ starts but after one to a few hours instead. At the moment the only way to resolve this at our end is to restart the AMQ.
        Environment Found on Windows but reproduced under Linux CentOS 5.2 64bit
        Fix Version/s 5.2.0 [ 11841 ]
        Component/s Broker [ 10763 ]
        Rob Davies made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Fix Version/s 5.3.0 [ 11914 ]
        Resolution Fixed [ 1 ]
        Jeff Turner made changes -
        Project Import Fri Nov 26 22:32:02 EST 2010 [ 1290828722158 ]

          People

          • Assignee:
            Rob Davies
            Reporter:
            Loc Truong
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development