activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tim Bain <>
Subject Re: - Transport Connection to: tcp://XX.XX.XXX.XXX:5445 failed:
Date Mon, 17 Apr 2017 13:11:05 GMT
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 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?
> The JIRA you linked to was specifically related to websockets; is that a
> configuration you're using?
> 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.
> BTW, kill -3 will generate a thread dump without needing to install
> additional software, but it generates it to standard out for the broker
> process, so it only helps if standard out has been redirected somewhere you
> can access it. So this might or might not be useful to you.
> Tim
> On Apr 16, 2017 10:28 PM, "Siebo" <> wrote:
> 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:
> 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:
> Transport-Transport-Connection-to-tcp-XX-XX-XXX-
> XXX-5n-tp4722840p4724978.html
> Sent from the ActiveMQ - User mailing list archive at

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message