Thanks you very much, Gary. I will specify client id and durable subscriber name explicitly so that broker host is not used in client id.
I am working on a setup where a broker will run on the cloud and change location from one host to another on restart. When this happens, the connection id, client id, producer id, consumer id, session id in case of STOMP clients (which is constructed based on broker host) may also change as the broker changes location. Our understanding is that most of these ids change upon broker/client restarts (sine even in today's fixed host world, port number, time etc changes) and does not affect anything. The only ids that matter to us are the client id and the durable subscription name since these are used in order for durable subscription protocol to work properly. These ids should remain same across broker/client restart -- only then broker would identify a client as a previously registered durable subscriber and deliver the required messages. I will specify explicit client id and durable subscriber name for durable subscriber so that this does not change on broker restart. However, other ids may still change. Do you see any issues/dependencies of running broker on the cloud and have the load balancer forward client requests to the required host? Any issue in other ids changing? -Sophia -- View this message in context: http://activemq.2283324.n4.nabble.com/Query-about-ActiveMQ-connection-id-and-client-id-format-tp4671843p4675655.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
