[AMQ-3525] Messages seem to be getting stuck on queues

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.5.0, 5.5.1
• Fix Version/s: 5.6.0
• Component/s: Broker

Environment

Red Hat Enterprise Linux 5, x86_64
apache-activemq-5.5-fuse-20110915.022452-46

• Assignee: Gary Tully
• Reporter: Peter Blackburn
• Created: 07/Oct/11 10:02
• Updated: 15/Feb/12 10:42
• Resolved: 15/Feb/12 10:41

Description

Running load test of our application using AMQ as the JMS provider, messages seem to get stuck on the queues. After load test was stopped, but application was still running and all consumers still connected to the AMQ server. Several minutes later, the queue sizes were:

QUEUE_A 2
QUEUE_B 3
QUEUE_C 3
QUEUE_D 1
QUEUE_E 33

Our application was then stopped and the AMQ server restarted. There were no consumers for any of the queues at this point. After restart, the queue sizes were as follows:

QUEUE_A 2
QUEUE_C 3
QUEUE_E 26

Spot checks of the messages remaining after broker restart appear to show that they were successfully consumed during the load test run, but are somehow still on the queues.

Issue Links

• requires: AMQ-3576 ProducerBrokerExchange last producer sequenceId initialization needs runtime updates to deal with possible duplicate resends