Re: | WARN | Transport Connection to: tcp://xx.xx.xx.xx:xxxxx failed

Dear Tim Thanks for always helping me understand ActiveMQ. As you told me, it's likely that pollings from an observation server and load balancers would be the reason of a lot of warns. And I'm sorry for not consulting the mailing list beforehand. I'm going to do it from now. Thanks. Hidekazu

Re: | WARN | Transport Connection to: tcp://xx.xx.xx.xx:xxxxx failed

TCP connections are always bi-directional; even if you don't pass application-layer content in one direction, you still have to send acks for the messages containing content coming in the other direction. There's another email thread ( http://activemq.2283324.n4.nabble.com/org-apache-activemq-brok

| WARN | Transport Connection to: tcp://xx.xx.xx.xx:xxxxx failed

Hi everyone. I want your help to understand what have happened on my ActiveMQ. I use AcitveMQ ver 5.14.3. I noticed that I had a lot of WARN logs on the ActiveMQ as follows. 2017-04-11 00:00:07,675 | WARN | Transport Connection to: tcp://10.0.2.8:47505 failed: java.io.EO