[
https://issues.apache.org/activemq/browse/AMQ-2632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63149#action_63149
]
Michael Zamir commented on AMQ-2632:
------------------------------------
Thank for the prompt and good answer:)
I've inserted the change in client side, as you suggested and it worked:
I'm using
failover:(tcp://michael:61616,tcp://luba:62616)?randomize=false&*updateURIsSupported=false*
And my client is no more updated with the full list of broker in my network.
Thanks again.
Michael.
> Update client connections with information about a cluster of networked
> brokers
> -------------------------------------------------------------------------------
>
> Key: AMQ-2632
> URL: https://issues.apache.org/activemq/browse/AMQ-2632
> Project: ActiveMQ
> Issue Type: Improvement
> Components: JMS client
> Affects Versions: 5.0.0, 5.1.0, 5.2.0, 5.3.0
> Reporter: Rob Davies
> Assignee: Rob Davies
> Fix For: 5.4.0
>
>
> Currently it is up to the client to decide which broker(s) it should connect
> to. It would be beneficial to allow clients to be informed of brokers
> joining/leaving a cluster of networked brokers, and optionally load balance
> across them.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
