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 case, > are all clients/brokers misbehaving equally, or are some fine and others > very unhappy? → I can tell that all consumers were working fine while EOFException occurred continuously. Pretty weird huh? > The JIRA you linked to was specifically related to websockets; is that a > configuration you're using? → I can't really get your idea. I made no configuration to ActiveMQ's activemq.xml other than using MySQL persistenceAdapter instead of kahaDB. So current configuration is using websockets I think. > I completely understand not being able to upgrade the version of ActiveMQ > on a production server, but I don't buy the argument that it's not > possible to take a thread dump just because it's a production server. > Taking a thread dump is not a performance impact, and you should push back > on whoever is telling you that you're not allowed to do it. Unless, of > course, you don't care about the thread count and only want to pursue the > EOFException question. → Yes, you're right. My problem is having no right to generate thread dump on production server. It had already been requested. I hope to receive the thread dump soon... > Also, what does the stack trace for the EOFException say the broker was > doing when the EOFException occurred? → The broker did nothing in this case I think. It just started and the EOFException appeared in log file and no message was sent into it (on 'inactive' ActiveMQ server). As I know, ActiveMQ InactivityMonitor would check for 'inactive' connection all the time. I wonder if it is the only job that broker was doing while EOFException occurred. Here are some lines of log, the EOFException was log about once a min: Thanks and best regards, Siebo -- View this message in context: http://activemq.2283324.n4.nabble.com/org-apache-activemq-broker-TransportConnection-Transport-Transport-Connection-to-tcp-XX-XX-XXX-XXX-5n-tp4722840p4725022.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.