I'm using QPID M2 with a C# client which publishes lots of data to it, one JMS client which publishes much smaller amount of data and Java and/or C# clients which read off some data.
I publish approximately the same amount of data every day; however, I receive the following errors just once in a while (I restart all my servers every morning). I'm trying to make sense of these errors. --How can I find out which queue breached? tmp_0234282whatever doesn't mean anything to me, it is created by one of the clients. I can't use JMX to find out where this queue is bound since the server is already dead by the time I see this. --Why does this happen? Clearly the queue is getting overfilled. Is this because data is not being read by the client fast enough? This sounds unlikely since my largest volume data is prices and quotes for about 100, mid to low liquidity stocks. My server hardware is medium sized server level hardware. I do notice that when I disconnect my client (I think only JMS client), I get a "session closed implictly: java.io.IOException: Connection reset by peer" error. This is despite the fact that I explicitly close the connection with calls to .close() on Connection. Is it possible that qpid doesn't realize that the client is no longer connected and keeps populating the queue...eventually causing these errors? --Errors-- 2008-07-17 16:25:29,793 INFO [pool-2-thread-6] queue.AMQQueueMBean (AMQQueueMBean.java:274) - MESSAGE_COUNT_ALERT On Queue tmp_033d4cd6-f0d7-42c4-8b20-ce4aa4d61378 - 5000: Maximum count on queue threshold (5000) breached. 2008-07-17 16:25:59,835 INFO [pool-2-thread-2] queue.AMQQueueMBean (AMQQueueMBean.java:274) - MESSAGE_COUNT_ALERT On Queue tmp_033d4cd6-f0d7-42c4-8b20-ce4aa4d61378 - 5386: Maximum count on queue threshold (5000) breached. 2008-07-17 16:26:29,883 INFO [pool-2-thread-2] queue.AMQQueueMBean (AMQQueueMBean.java:274) - MESSAGE_COUNT_ALERT On Queue tmp_033d4cd6-f0d7-42c4-8b20-ce4aa4d61378 - 5786: Maximum count on queue threshold (5000) breached. 2008-07-17 16:26:59,924 INFO [pool-2-thread-3] queue.AMQQueueMBean (AMQQueueMBean.java:274) - MESSAGE_COUNT_ALERT On Queue tmp_033d4cd6-f0d7-42c4-8b20-ce4aa4d61378 - 6186: Maximum count on queue threshold (5000) breached. 2008-07-17 16:27:29,966 INFO [pool-2-thread-1] queue.AMQQueueMBean (AMQQueueMBean.java:274) - MESSAGE_COUNT_ALERT On Queue tmp_033d4cd6-f0d7-42c4-8b20-ce4aa4d61378 - 6586: Maximum count on queue threshold (5000) breached. 2008-07-17 16:28:00,005 INFO [pool-2-thread-8] queue.AMQQueueMBean (AMQQueueMBean.java:274) - MESSAGE_COUNT_ALERT On Queue tmp_033d4cd6-f0d7-42c4-8b20-ce4aa4d61378 - 6986: Maximum count on queue threshold (5000) breached. 2008-07-17 16:28:30,046 INFO [pool-2-thread-4] queue.AMQQueueMBean (AMQQueueMBean.java:274) - MESSAGE_COUNT_ALERT On Queue tmp_033d4cd6-f0d7-42c4-8b20-ce4aa4d61378 - 7386: Maximum count on queue threshold (5000) breached. 2008-07-17 16:29:00,086 INFO [pool-2-thread-2] queue.AMQQueueMBean (AMQQueueMBean.java:274) - MESSAGE_COUNT_ALERT On Queue tmp_033d4cd6-f0d7-42c4-8b20-ce4aa4d61378 - 7786: Maximum count on queue threshold (5000) breached. 2008-07-17 16:29:30,129 INFO [pool-2-thread-6] queue.AMQQueueMBean (AMQQueueMBean.java:274) - MESSAGE_COUNT_ALERT On Queue tmp_033d4cd6-f0d7-42c4-8b20-ce4aa4d61378 - 8186: Maximum count on queue threshold (5000) breached. 2008-07-17 16:30:00,167 INFO [pool-2-thread-2] queue.AMQQueueMBean (AMQQueueMBean.java:274) - MESSAGE_COUNT_ALERT On Queue tmp_033d4cd6-f0d7-42c4-8b20-ce4aa4d61378 - 8586: Maximum count on queue threshold (5000) breached. 2008-07-17 16:30:30,207 INFO [pool-2-thread-4] queue.AMQQueueMBean (AMQQueueMBean.java:274) - MESSAGE_COUNT_ALERT On Queue tmp_033d4cd6-f0d7-42c4-8b20-ce4aa4d61378 - 8986: Maximum count on queue threshold (5000) breached. 2008-07-17 16:31:00,252 INFO [pool-2-thread-5] queue.AMQQueueMBean (AMQQueueMBean.java:274) - MESSAGE_COUNT_ALERT On Queue tmp_033d4cd6-f0d7-42c4-8b20-ce4aa4d61378 - 9386: Maximum count on queue threshold (5000) breached. Thanks
