The EOF exception does mean the client closed the socket without properly shutting down the ActiveMQ Connection.
>From the client log snippet posted, it's unclear what's causing the same. Is it possible to attach a debugger to the client and put a break-point at the point the disconnect occurs? If neither the client nor the broker initiated the disconnect, perhaps there's a network hickup causing the same. -- View this message in context: http://activemq.2283324.n4.nabble.com/activemq-client-does-not-close-properly-connections-to-the-broker-tp4681005p4681006.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
