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.