Re: org.apache.activemq.broker.TransportConnection.Transport - Transport Connection to: tcp://XX.XX.XXX.XXX:5445 failed: java.io.EOFException

That's great news. Sorry for never responding to your last two emails; I still had them flagged to come back to, but nothing in the thread dump gave me any idea of what was going on. Now that you've determined that the behavior was driven by external forces rather than something within the broker,

Re: org.apache.activemq.broker.TransportConnection.Transport - Transport Connection to: tcp://XX.XX.XXX.XXX:5445 failed: java.io.EOFException

Hi, Finally, my problem was solved. It was a mistake from load balance tool which made continuous command call to check activemq alive or not. By some reasons, it made the number of thread increase by time and activemq die when it exceeded maximum threads. Thank you all (especially Tim) did help m

Re: org.apache.activemq.broker.TransportConnection.Transport - Transport Connection to: tcp://XX.XX.XXX.XXX:5445 failed: java.io.EOFException

Hi Tim, After quite long time, I got the thread dumps. I attach only one of 'master' ActiveMQ machine. thread_dump.log Here are weird info I noticed from thread_dump: - There are 4955 threads in WAITING state. - Most of them (

Re: org.apache.activemq.broker.TransportConnection.Transport - Transport Connection to: tcp://XX.XX.XXX.XXX:5445 failed: java.io.EOFException

Hi Tim, Sorry I could not reply soon because of some errors from nabble forum on last Friday. > So are all client IPs represented proportionally in the EOFExceptions? No, just only one consumer represented EOFException in ActiveMQ's log. That consumer is running on the same machine with the bro

Re: org.apache.activemq.broker.TransportConnection.Transport - Transport Connection to: tcp://XX.XX.XXX.XXX:5445 failed: java.io.EOFException

Siebo, On Apr 18, 2017 4:28 AM, "Siebo" wrote: Hi Tim, > OK, for the EOFException, are your brokers behind a load balancer like > this thread's OP was? It sounds like you're not, so what's on the other > end of those connections? One possibility is real client processes, or > another is anothe

Re: org.apache.activemq.broker.TransportConnection.Transport - Transport Connection to: tcp://XX.XX.XXX.XXX:5445 failed: java.io.EOFException

Hi Tim, > OK, for the EOFException, are your brokers behind a load balancer like > this thread's OP was? It sounds like you're not, so what's on the other > end of those connections? One possibility is real client processes, or > another is another broker in a network of brokers setup. In either

Re: org.apache.activemq.broker.TransportConnection.Transport - Transport Connection to: tcp://XX.XX.XXX.XXX:5445 failed: java.io.EOFException

Also, what does the stack trace for the EOFException say the broker was doing when the EOFException occurred? On Apr 17, 2017 7:01 AM, "Tim Bain" wrote: > OK, for the EOFException, are your brokers behind a load balancer like > this thread's OP was? It sounds like you're not, so what's on the ot

Re: org.apache.activemq.broker.TransportConnection.Transport - Transport Connection to: tcp://XX.XX.XXX.XXX:5445 failed: java.io.EOFException

OK, for the EOFException, are your brokers behind a load balancer like this thread's OP was? It sounds like you're not, so what's on the other end of those connections? One possibility is real client processes, or another is another broker in a network of brokers setup. In either case, are all clie

Re: org.apache.activemq.broker.TransportConnection.Transport - Transport Connection to: tcp://XX.XX.XXX.XXX:5445 failed: java.io.EOFException

Hi Tim, First, I want to say thank you for your help. I would like to update more information for this trouble: I have 2 machines running ActiveMQ as Master-Master (for some reason, I used another tool to detect which machine would be used as 'active', while the other would be 'inactive' instead o

Re: org.apache.activemq.broker.TransportConnection.Transport - Transport Connection to: tcp://XX.XX.XXX.XXX:5445 failed: java.io.EOFException

An EOFException is an indication that the OS believes that the socket is closed, so at the socket level, the OS will not hold onto large numbers of sockets under the conditions you describe. You can confirm this by using netstat to see how many sockets are open when you reach (or approach) the fai

Re: org.apache.activemq.broker.TransportConnection.Transport - Transport Connection to: tcp://XX.XX.XXX.XXX:5445 failed: java.io.EOFException

I'm facing the same problem and after 2-3 days, ActiveMQ stopped because of OutOfMemoryError on broker side: After doing some research, I have some theories: - TCP connection with EOFException cannot be closed. - Each TCP connection was run under a separate thread, so the thread cannot be destro

Re: org.apache.activemq.broker.TransportConnection.Transport - Transport Connection to: tcp://XX.XX.XXX.XXX:5445 failed: java.io.EOFException

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" wrote: Yes this Sever is configu

Re: org.apache.activemq.broker.TransportConnection.Transport - Transport Connection to: tcp://XX.XX.XXX.XXX:5445 failed: java.io.EOFException

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 wrote: > > Check if the

Re: org.apache.activemq.broker.TransportConnection.Transport - Transport Connection to: tcp://XX.XX.XXX.XXX:5445 failed: java.io.EOFException

Check if the IP 10.33.168.186 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 wrote: > We have following Configuration in Activemq.XML > > > > >

org.apache.activemq.broker.TransportConnection.Transport - Transport Connection to: tcp://XX.XX.XXX.XXX:5445 failed: java.io.EOFException

We have following Configuration in Activemq.XML 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] WAR