activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From artnaseef <...@artnaseef.com>
Subject Re: already connected from tcp://xx.xxx.x.xxx:59357
Date Sat, 15 Feb 2014 00:59:24 GMT
Is the client code setting a Client ID on the connection via setClientID()?

http://docs.oracle.com/javaee/1.4/api/javax/jms/Connection.html#setClientID(java.lang.String)

If so, then only one connection with a specific client ID can connect to the
broker/network-of-brokers at any one time.  Given the error message
indicating already connected, you can see from where the other connection is
being made.

If that's the same machine and the same JVM, check for a connection pool, or
connection leak on the client.




--
View this message in context: http://activemq.2283324.n4.nabble.com/already-connected-from-tcp-xx-xxx-x-xxx-59357-tp4678001p4678008.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Mime
View raw message