RE: Could you try your scenario with the current 5.6 release to see if it is
still reproducible.
Just tried it and yes, it still reproducable. I found your blog (thanks!)
about the prefetch size and the negative number for the queue count.
Confirmed that the negative value is smaller when going
that looks like a sync issue between the jmx op and the destination
w.r.t counters.
Possibly messages that are dispatched and inflight to the consumer are
getting removed so they are acked twice.
inflight messages should really be invisible to a remove message call
via jmx but I guess that is debat
Hi All,
We are running into a case where our queue size is < 0 via both the
webconsole and via jmx in 5.3.2. Here is our scenario:
VM1: looping 5000 times, each time pushing a message into a queue
VM2: listening on the queue (1 listener) and processing the messages
VM2: responds to a REST call b
