i was hoping this was the case and that the killed process was saying a last goodbye on the way out.
this is a nice behavior. i've just recently run similar tests using hornetq where killing the java process (or having it crash) did not result in the server becoming aware so quickly. i certainly prefer the behavior provided by the activemq tcp transport. -- View this message in context: http://activemq.2283324.n4.nabble.com/trying-to-understand-exactly-how-the-server-knows-when-a-client-fails-tp3047186p3047440.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
