Uploaded image for project: 'ActiveMQ Classic'
  1. ActiveMQ Classic
  2. AMQ-4052

When consumers was killed and restarted frequently, some messages could not be consumed by consumer but they were still in pending messages.



    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 5.6.0
    • 5.7.0
    • Broker
    • None
    • CentOS release 5.6 (Final) java version "1.6.0_30"


      The phenomenon of the bug:
      When consumers was killed and restarted frequently, some messages could not be consumed by consumer but they were still in pending messages.

      When consumer consumes messages in transaction, it sends ack command and transaction commit command separately, if the consumer was killed between ack command and transaction commit command, in other words the Broker only received the ack command but did not receive the transaction commit command, this lead to the message in PrefetchSubscription’s dispatched list was set ack true, but was not removed from dispatched list. When the consumer was killed, Queue#removeSubscription() was called, in this method, PrefetchSubscription#remove() was called to put PrefetchSubscription’s pending list and dispatched list to Queue’s redeliveredWaitingDispatch list. After that, when Queue#doDispatch() was called, the redeliveredWaitingDispatch list was transferred to Queue#doActualDispatch () method to dispatch the messages to consumer again. In Queue#doActualDispatch () method, if all consumers isFull() method returns true, the target is null and the expression “interestCount > 0” become the only condition to judge if the message should be put back to the redeliveredWaitingDispatch, but now the message’s isAcked() method returns true, this lead to interestCount is 0, and then the message was not put back to redeliveredWaitingDispatch, but it was not consumed and was still in pagedInMessages.

      In PrefetchSubscription#remove() method, set ack status to false for all messages in dispatched list. The code as follows:

          public List<MessageReference> remove(ConnectionContext context, Destination destination) throws Exception {
              List<MessageReference> resultList = new ArrayList<MessageReference>();
              synchronized(pendingLock) {
                  super.remove(context, destination);
                  // Here is a potential problem concerning Inflight stat:
                  // Messages not already committed or rolled back may not be removed from dispatched list at the moment
                  // Except if each commit or rollback callback action comes before remove of subscriber.
                  resultList.addAll(pending.remove(context, destination));
                  // Synchronized to DispatchLock
                  synchronized(dispatchLock) {
                      ArrayList<MessageReference> references = new ArrayList<MessageReference>();
                      for (MessageReference msgRef : dispatched) {
                          if( msgRef.getRegionDestination() == destination) {
                              if (msgRef instanceof QueueMessageReference) {
                              	QueueMessageReference ref = (QueueMessageReference) msgRef;
              return resultList;

      The solution can solve the problem, I want to know if the solution can lead to other problems.




            Unassigned Unassigned
            vivian58659 Wei Wei
            0 Vote for this issue
            4 Start watching this issue