activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Posta <christian.po...@gmail.com>
Subject Re: Dynamic discovery for client libraries
Date Tue, 27 May 2014 16:03:36 GMT
Then you have to manage the discovery parts yourself. You can look here:

http://activemq.apache.org/discovery.html

There is also an http discovery mechanism.

Fabric8 handles this for you.


On Mon, May 26, 2014 at 1:31 AM, master.zakharov
<master.zakharov@gmail.com>wrote:

> Noel, thanks for the info about fabric8, will check it out.
>
> What regarding the MQTT - do not know as well whether it is feasible within
> the protocol to pass the clustering info. But I do not limit the scenario
> to
> MQTT only, it was only as example of let's say external client.
>
> What do I want to achieve is to accomplish the dynamic discovery, manage it
> explicitly, and do not introduce a gateway/load-balancer in front of
> broker.
>
> So I wonder what ActiveMQ could provide here. Beside from Advisory messages
> I checked the JMX interface of ActiveMQ:
>  - I can receive the number of brokers in the cluster - brokers are
> establish tcp connection between each other (clientConnectors / tcp /
> clientId / ...)
>  - but for the moment this info is not enough for dynamic discovery,
> because
> that info does not contain the info about available connectors for specific
> transport/protocol
>
> And I did not found the exhaustive documentation for ActiveMQ JMX.
> http://activemq.apache.org/jmx.html - only overview
>
> http://apache.apache.org/maven/activemq-core/apidocs/org/apache/activemq/broker/jmx/package-summary.html
> - 404
>
> Thanks,
> Konstantin
>
>
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Dynamic-discovery-for-client-libraries-tp4681303p4681393.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>



-- 
*Christian Posta*
http://www.christianposta.com/blog
twitter: @christianposta

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message