Thanks. You are right, the server doesn't actually die. However, after I receive the "queue breached" message, my clients are not able to successfully connect.
If the broker has this information, perhaps the error message could print what topic/exchange the queue was bound to. By the way, if I want to use my C# client as well, what is the latest usable release I should be using? Anything more recent than the M2? Is the RedHat MRG release based on M2 or later? Thanks again. -----Original Message----- From: Robert Greig [mailto:[EMAIL PROTECTED] Sent: Thursday, July 17, 2008 4:50 PM To: [email protected] Subject: Re: Maximum count on queue threshold breached 2008/7/17 Shahbaz Chaudhary <[EMAIL PROTECTED]>: > 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. This is something that has been discussed previously. I am not sure if this made it into the M2.x codebase or whether it is slated for trunk. Maybe someone who was involved in that discussion can give us an update? However I don't understand why "the server is dead"? The message is informational and the server should be working normally. > --Why does this happen? Clearly the queue is getting overfilled. Is > this because data is not being read by the client fast enough? Yes. > 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? I don't think we have seen that error before. The server has clearly detected the client has disconnected so it should clean up the temp queue. Even if you were not calling close() it should still work fine. It would be interesting to check using the management console (or JMX directly) that the number of connections and queues/bindings to the topic exchange are as you expect. RG
