Confirmed.. if you don't clean up your session and connection cleanly, the
broker will warn for you. Its usually indicative of a client that is mis-coded.
Look for exceptions being thrown.. a lot of times folks don't have the finally
{ } block defined to clean up JMS objects.
Also.. check out
I believe that those exceptions occur when a client does not
disconnect from the broker gracefully.
Verify that your client is making the appropriate close call on the
connection. Do you have STOMP based clients that are frequently
connecting and disconnecting?
Thanks,
Paul
On Wed, Oct 23, 2013
Hi. Hoping that someone might have some insight into what we're seeing in our
activemq.log file.
We're running ActiveMQ 5.8 and in the activemq.log file we see lots of messages
like this:
2013-10-11 09:03:57,212 | WARN | Transport Connection to:
tcp://10.251.128.28:42015 failed: java.io.EOFEx
