When the socket timeout happens, you do get notified via onException() - I just verified this. However as soon as the "read timeout" happens the connection is also closed, and another exception is generated. Therefore you are most likely to see the "connection aborted" exception from your listener than the "read timeout".
I think it's more desirable if the "read timeout' exception is thrown rather than the connection closed. (But please note that the "Read Timeout" exception is logged, so information is not lost) On Tue, May 4, 2010 at 6:18 PM, Wes Parish <w...@firstshotprecision.com> wrote: > When a connection exception is thrown because of a socket timeout exception, > which occurs when a heartbeat times out, it is not being sent to the > onException() method. Should this exception be sent like the others to this > method? > > Wes > -- Regards, Rajith Attapattu Red Hat http://rajith.2rlabs.com/ --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:users-subscr...@qpid.apache.org
