Yes, you can ignore those warnings from the load balancer's IP, but you will still want to look at them for all other IPs. And no, you don't need to make any configuration changes.
Good call Ravi on the load balancer. Tim On Mar 5, 2017 10:04 PM, "Daivish.shah" <daivish.s...@gmail.com> wrote: Yes this Sever is configured to F5 load balancer too, does that mean I need to ignore the message something like this ?! Do I need to make any changes in my configurations here ?! Please advice me thanks for your help on this. > On Mar 5, 2017, at 8:55 PM, Ravi Kumar <rakare2...@gmail.com> wrote: > > Check if the IP 10.33.168.186 <http://10.33.168.186:5445/> belongs to any > load balancer. If so then if healthcheck is enabled at load balancer level > then you will get such messages. > >> On Sat, Mar 4, 2017 at 4:30 AM, Daivish Shah <daivish.s...@gmail.com> wrote: >> >> We have following Configuration in Activemq.XML >> >> >> <networkConnectors> >> >> <networkConnector >> >> name="topic-project-mq-stg1-node1" >> >> uri="static:(tcp://node1.abcl.com:6162 >> )?maxReconnectDelay=5000&useExponentialBackOff=false;" >> >> duplex="false" >> >> decreaseNetworkConsumerPriority="true" >> >> networkTTL="2" >> >> dynamicOnly="true"> >> >> <excludedDestinations> >> >> <queue physicalName=">" /> >> >> </excludedDestinations> >> >> </networkConnector> >> >> <networkConnector >> >> name="queue-project-mq-stg1-node1" >> >> uri="static:(tcp://node1.abcl.com:6162 >> )?maxReconnectDelay=5000&useExponentialBackOff=false;" >> >> duplex="true" >> >> decreaseNetworkConsumerPriority="true" >> >> networkTTL="2" >> >> dynamicOnly="true"> >> >> <excludedDestinations> >> >> <topic physicalName=">" /> >> >> </excludedDestinations> >> >> </networkConnector> >> >> </networkConnectors> >> >> >> >> It's throwing following Errors in the log files continuously - Can you >> please explain this issue ? IT this is a BUG in the ActiveMQ code ? >> >> >> *2017-03-03 13:54:13,425 [ActiveMQ Transport: >> tcp:///XX.XX.XXX.XXX:42738@6162] WARN >> org.apache.activemq.broker.TransportConnection.Transport - Transport >> Connection to: tcp://10.33.168.186:5445 <http://10.33.168.186:5445> >> failed: >> java.io.EOFException* >> >> >> *Please Advice to resolve this issue. * >> >> >> *Thanks,* >> >> *Daivish. * >>
