[
https://issues.apache.org/jira/browse/AMQ-3525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122811#comment-13122811
]
Gary Tully commented on AMQ-3525:
---------------------------------
would it be possible to simplify your load test and still be able to reproduce
this observation?
After a restart, when there are 2,3,26 messages, is it possible to consume
these messages?
If so, they would be considered duplicates from the application perspective,
correct?
The reason I ask is to determine if the problem is related to skipped messages
or destination counters.
The key to getting to the bottom of this is some test code or a description
that can reproduce, and ideally reliably.
> Messages seem to be getting stuck on queues
> -------------------------------------------
>
> Key: AMQ-3525
> URL: https://issues.apache.org/jira/browse/AMQ-3525
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.x
> Environment: Red Hat Enterprise Linux 5, x86_64
> apache-activemq-5.5-fuse-20110915.022452-46
> Reporter: Peter Blackburn
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
