Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (athena.apache.org: domain of mrdavidoc@gmail.com
 designates 209.85.216.173 as permitted sender)
MIME-Version: 1.0
Date: Sun, 22 Sep 2013 12:32:37 +0100
Message-ID: 
 <CAK0PmvgmFsUZO9GMC0XrZFO8CaXjbfmXchxR-H3N4mJzKXLKBQ@mail.gmail.com>
Subject: ActiveMQ - 5.5.1, connections stuck at CLOSE_WAIT, reaching file
 descriptor limit
From: "David O'C" <mrdavidoc@gmail.com>
To: users@activemq.apache.org
Content-Type: multipart/alternative; boundary=047d7b621ac8b9baa304e6f742a8

--047d7b621ac8b9baa304e6f742a8
Content-Type: text/plain; charset=ISO-8859-1

Hi,

I have seen an issue seen where ActiveMQ 5.5.1 would keep outbound
connections in a CLOSE_WAIT state, to the point where the application
reaches the file descriptor limit.

The broker uses the Openwire format on TCP with closeAsync set to false.
 It is also non-persistant, storing all messages within memory.

The fault is infrequent, I've been unable to reproduce this on-demand.
 I've searched and I've been unable to see any re-occurance of this issue
on the same version.

I've read that this issue was seen before in previous releases, could this
be the same issue seen?

Regards,
David

--047d7b621ac8b9baa304e6f742a8--