Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: softfail (nike.apache.org: transitioning domain of
 master.zakharov@gmail.com does not designate 216.139.250.139 as permitted
 sender)
Date: Wed, 21 May 2014 06:40:39 -0700 (PDT)
From: "master.zakharov" <master.zakharov@gmail.com>
To: users@activemq.apache.org
Message-ID: <1400679639784-4681303.post@n4.nabble.com>
Subject: Dynamic discovery for client libraries
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hello

I'd like to evaluate the approach with failover and dynamic discovery of
ActiveMQ brokers for "client" libraries, i.e. not the one using the
ActiveMQConnection, e.g. some libraries for MQTT protocol.

For ActiveMQConnection's I may use the "failover://" protocol and in case of
"updateClusterClients=true" option, the client need to know only about one
broker to connect to.

And how it can be achieved e.g. for MQTT?

Are there some system topic the client can subscribe to and be notified
about some broker in the cluster become (un)available? I checked the
documentation for Advisory messages, but there are no messages related to
cluster changes.

And even if such topic exists, how can I get the initial list of brokers in
the cluster?

I hope the dynamic discovery is feasible, and someone could give me the
reference to the documentation or code samples. 

Thanks in advance,
Konstantin


--
View this message in context: http://activemq.2283324.n4.nabble.com/Dynamic-discovery-for-client-libraries-tp4681303.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.