You might be on to it. But I would recommend you use jconsole to monitor the JMX stats of the server. Keep an eye on the broker's memory percentage used. Once this hits 100% it stops accepting messages from the producers.
On 8/3/06, sparky2708 <[EMAIL PROTECTED]> wrote:
As I was walking home tonight it hit me it could be my client. I think that a possible explanation for what I am seeing is: Perhaps my client keeps up with messages from the producer in the beginning and then it deadlocks somewhere when it receives too many messages. Then I kill the client and try to bring it back up at which point the broker pummels the client with all the messages that the client had missed since it crashed and the deadlock happens again. So no matter how many times I restart the client it will deadlock because the broker is flooding it with messages. After I restart the broker the client works OK for awhile. Might be what's happening... Will take a look tomorrow at my locks... -- View this message in context: http://www.nabble.com/Openwire.NET-crashes-ActiveMQ-broker-tf2048174.html#a5643196 Sent from the ActiveMQ - User forum at Nabble.com.
-- Regards, Hiram Blog: http://hiramchirino.com
