Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: softfail (nike.apache.org: transitioning domain of
 cwiklik@us.ibm.com does not designate 216.139.250.139 as permitted sender)
Date: Mon, 19 Aug 2013 13:57:51 -0700 (PDT)
From: Jerry Cwiklik <cwiklik@us.ibm.com>
To: users@activemq.apache.org
Message-ID: <1376945871591-4670498.post@n4.nabble.com>
In-Reply-To: 
 <CAKS7T5O-Y1V1f4_zDr9Wk+9Tb5N0KEpN9S+yZquh9iHBrErung@mail.gmail.com>
References: <1376941859890-4670496.post@n4.nabble.com>
 <CAKS7T5O-Y1V1f4_zDr9Wk+9Tb5N0KEpN9S+yZquh9iHBrErung@mail.gmail.com>
Subject: Re: Broker leaks FDs - Too many open files
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Christian, thanks. More questions:

What would be your theory why we see the "explosion" of open FDs? This is
triggered by some event. Any clues as to what that might be? 

Also, isnt it a bug that the broker just goes bezerk logging the same thing
over and over? Our broker's logs are filled with the error below. I suspect
that perhaps Camel or Spring which are used on the client side are in some
recovery mode trying to establish a connection to the broker which keeps
failing. 

2013-07-28 00:04:08,264 [teTimeout=45000] ERROR TransportConnector            
- Could not accept connection : java.net.SocketException: Too many open
files
 ..

What are the consequences of using closeAsync="false"? 

JC


--
View this message in context: http://activemq.2283324.n4.nabble.com/Broker-leaks-FDs-Too-many-open-files-tp4670496p4670498.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.