Details of the inactivity monitor are at http://activemq.apache.org/activemq-inactivitymonitor.html. It's on by default, so if you haven't modified any settings related to it, it should be working correctly.
An EOFException typically means that something closed the TCP connection. Often it's the program on the other end (if you're seeing this in the client, then the broker may have closed it, or vice versa), so check that program's logs to see if they tell you anything. It can also happen because the other process was hard-killed (kill -9), or because a firewall between the broker and the client killed the connection, or probably other things as well. If it happens infrequently and your clients reconnect to the broker and resume processing without incident, then you can safely ignore it if you want. If you don't want to ignore it and you want to dig into what's going on, I'd start with both logs (client and broker), and if you can't see anything in them then I'd probably try using WireShark to figure out what's going on at the TCP layer and then go from there. Tim On Fri, Jul 14, 2017 at 7:13 PM, akpuvvada <akp4ti...@gmail.com> wrote: > I have not configured any inactivity monitoring. How can I check if any > exists by default? > > > > -- > View this message in context: http://activemq.2283324.n4. > nabble.com/Transport-failed-attempting-to-automatically- > reconnect-due-to-java-io-EOFException-tp2351687p4728568.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
