What version of ActiveMQ are you using?
There have been a number of bug fixes around duplicate detection in the past
few releases.
Perhaps you got some duplicate messages in your store that the cursor would not
dispatch because it detected them as duplicates.
This should generally not happen,
Torsten, All our brokers are on 5.7.0.
I'm wondering if this is to do with a Stomp client which specifies a
prefetch limit of 200 which processes 200 msgs then disconnects. It is
invoked by a scheduled job manager. I've changed this prefetch limit 1 now
to see if it makes a difference under load
Hi James,
Theoretically the prefetch should not cause such problem. If it does, its a
bug.
On Nov 5, 2012, at 11:29 AM, James Green wrote:
Torsten, All our brokers are on 5.7.0.
I'm wondering if this is to do with a Stomp client which specifies a
prefetch limit of 200 which processes
I restarted AMQ. The counter remains at 55. Browsing, I now see messages!
They are 40 minutes old and have redelivery true. Is there anything more
that can be suggested as a result?
On 2 November 2012 15:14, James Green james.mk.gr...@gmail.com wrote:
I am looking at the web console and the
