activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Siebo <blacktora...@gmail.com>
Subject Re: org.apache.activemq.broker.TransportConnection.Transport - Transport Connection to: tcp://XX.XX.XXX.XXX:5445 failed: java.io.EOFException
Date Mon, 17 Apr 2017 04:18:48 GMT
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 of using JDBC Master-Slave). I named them
mq1 and mq2.
Currently, mq1 is in 'active' while mq2 is in 'inactive' state.
EOFException was logged continuously in both machines' log file.

I did a number of processes check by executing command:
top -H
Result:
mq1 (active): 5381 (2 running, 5379 sleeping)
mq2 (inactive): 277 (1 running, 276 sleeping)

EOFException seems not to be the reason for OutOfMemoryError anymore.
I wonder if a thread leak occurred in mq1, as described in this ticket:
https://issues.apache.org/jira/browse/AMQ-6482.

Because these machines are being used in production purpose, I cannot
generate thread dump or upgrade ActiveMQ version unless having an exact
conclusion.

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-tp4722840p4724978.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Mime
View raw message