In fact, this always happens when a connection stops... If you have a network of brokers and you stop one, you'll see this exception in the other brokers. If your client stops, same... Maybe this exception deserves to be handled like "Connection <name> has disconnected." but apart from that... it's a warning, and not severe afaics.
-- View this message in context: http://activemq.2283324.n4.nabble.com/Activemq-EOFException-tp4681252p4718765.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
