activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From artnaseef <Arthur.Nas...@Ticketmaster.com>
Subject Re: large number of connections from the same client
Date Thu, 02 Jan 2014 05:37:04 GMT
First I would check a couple of things to confirm the connections:

1. Check the web console and/or MBeans (jconsole or visualvm) to confirm the
number of connections from the client.
2. Check the O/S for the number of connections using netstat (something like
this on Linux: netstat -an | grep 61616.  Or this: netstat -an | grep 6161 |
awk '{ print $5 }' | sed -e 's,::ffff:,,' -e 's,:[0-9]*$,,' | sort | uniq
-c)
3. Check the O/S state of the connections (are they all open?)
4. Check the client system for the same.

If the connects are in fact active from the client, then solving the case is
a matter of looking at the client configuration.  A misconfigured client can
easily cause this problem.  It's easy to create large numbers of connections
with connection pools.

Inactive connections from the client (especially sockets in CLOSED_WAIT
state) indicate either the client or server failed to close the socket
properly.  There's a known issue with the same using SSL in java 1.6 (I
think it's fixed in 1.7).

On the other hand, if the connections exist in the broker but not at the O/S
level, then it's time to look for a leak.



--
View this message in context: http://activemq.2283324.n4.nabble.com/large-number-of-connections-from-the-same-client-tp4675871p4675919.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

Mime
View raw message