[jboss-user] [Remoting] - Re: Messaging blocked by long time-out

[ron.sigal@jboss.com]

I have a question.  

On the server side, there is an org.jboss.remoting.Lease which, if it doesn't receive pings from the client in a timely fashion, will declare that a connection is broken and inform any registered listeners.  Now JBossMessaging registers a listener, so it should be informed about the broken connection, and it should attempt to shut it down.  Now, Remoting won't try to kill a Socket in the middle of a read() or write(), but I'm a little surprised that JBossMessaging doesn't clean things up enough to prevent all the other clients from receiving messages.

Are you seeing the output from


  |   log.trace("Notified connection listener of lease expired due to lost connection from client (client session id = " + clientHolder.getSessionId());
  | 

on your server logs?

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4219349#4219349

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4219349