Hi every body I would want to be able to easily identify each of my TCP distant connection to my brokers without having to program anything on the client side.
I imagine using the jms.clientId on the client side with "tcp://myhost:xxxx?jms.clientID=myProject" as the connection URL, and catching AdvisoryMessage (ActiveMQ.Advisory.Connection) with another JMS "administrative" connection on the same broker. By this way, I hope that advisory messages received by my "administrative" connection, gives me the information that "myProject" justconnected or just disconnected. I imagine that connectionInfo structure is the core message that is present on the topic at each connection, but the documentation (http://activemq.apache.org/advisory-message.html) doesn't mention it clearly. Is it a good and supported way to detect and identify connections ? What would happen if 2 connections simultaneously use the same clientID ? Thank you Eric-AWL -- View this message in context: http://activemq.2283324.n4.nabble.com/Connection-ClientId-Identifier-and-AdvisoryMessage-tp3399952p3399952.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
