activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tim Bain <tb...@alumni.duke.edu>
Subject Re: "long time to shutdown" and "Broken pipe (Write failed)" broker issues
Date Thu, 29 Jun 2017 18:23:08 GMT
For #1, Gary suggested that you take a thread dump (or better, use a
sampler such as JVisualVM) to determine where the time is being spent. That
suggestion still holds.

On May 31, 2017 5:06 AM, "Andrei Shakirin" <ashakirin@talend.com> wrote:

> Hi,
>
> I am a happy ActiveMQ user for a long time and need suggestion regarding
> two issues (ActiveMQ 5.13.4, configured with shared NFS, Linux)
> 1) https://issues.apache.org/jira/browse/AMQ-6589
>    Long shutdown (or hanging) the broker with "The connection to
> 'tcp://xxx:55057' is taking a long time to shutdown." message.
>    Accordingly AMQ-3435, AMQ-3293, AMQ-4073 tickets the issue have to be
> fixed in AMQ 5.13.4, but is still occurs.
>
> 2) https://issues.apache.org/jira/browse/AMQ-6692
>     Hanging broker hanging with broken-pipe InactivityMonitor message:
>     "Transport Connection to: tcp://172.26.244.182:37994 failed:
> java.net.SocketException: Broken pipe (Write failed) |
> org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ
> InactivityMonitor Worker"
>
> Any suggestion how to proceed / work around of these issues?
>
> Regards,
> Andrei.
>

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