Given the netstat results, the problem does not appear to be related to the broker - the clients have opened the connections.
The pooled connection factory snippet looks OK. So, the next step is to track down the source of the connections in the client. A more complete review of the configuration may help. Analyzing a heap dump may help as well - looking for the references to the connections to understand why they exist. Running the application in a debugger with a breakpoint on the constructors for ActiveMQConnection could do the trick as well. -- View this message in context: http://activemq.2283324.n4.nabble.com/large-number-of-connections-from-the-same-client-tp4675871p4676008.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
