You will find a lot if issues like this. I highly recommend the use of
monitoring.
My current project does just that using jmxtrans, opentsdb, and metrilyx.
Make sure to watch for slow consumption!
Oh, and you are welcome ;-)
Sent from my iPhone
> On Mar 9, 2014, at 8:01 AM, "sansjunk [via
@artnaseef, thanks for the quick response - I didn't expect a reply over the
weekend so didn't bother to check sooner :-)
Yes, you are correct. Both the QueueSize and the PendingQueueSize of the
Queues and Topics respectively are 0.
The client side is JMS and looking at the code I did find the bu
Great writeup of your problem.
First off, ignore enqueue count on Topics; the number is purely "advisory".
Topics never store messages - only Queues and Topic Subscriptions store
messages. You can see this via JMX: Queues have a QueueSize attribute, and
Topic Subscriptions have a PendingQueueSiz
