[
https://issues.apache.org/jira/browse/AMQ-3707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13453028#comment-13453028
]
Gary Tully commented on AMQ-3707:
---------------------------------
thinking that an attribute {code}clusterClientsURIQuery{code} on the transport
connector would make sense, it would get appended to whatever is the
publishable address of the transport for update cluster client information.
This avoids the transport server having to deal with the query parameters and
leaves them opaque.
> Dynamic Failover Client Connection Params Broker Side Attribute
> ---------------------------------------------------------------
>
> Key: AMQ-3707
> URL: https://issues.apache.org/jira/browse/AMQ-3707
> Project: ActiveMQ
> Issue Type: New Feature
> Components: Broker
> Reporter: Scott England-Sullivan
> Fix For: 5.7.0
>
>
> Given that dynamic failover allows for the addition and removal of brokers
> from a list of available connections at the client, I would suggest that an
> attribute be made available on the broker to define what connection options a
> client should use when connecting to a given broker.
> Therefore a client with the following list of connections:
> Client connect string
> * failover://(tcp://somebrokerA:61616,tcp://somebrokerB:61616)
> And a broker with the following
> * (NEW) *clusterClientsConnectionParams="useCompression=true"*
> Would result in a client with the following connection list:
> * tcp://somebrokerA:61616?clusterClientsConnectionParams="useCompression=true"
> * tcp://somebrokerB:61616?clusterClientsConnectionParams="useCompression=true"
> And should a new broker be added to the cluster (if this option was set on
> each broker):
> * tcp://somebrokerA:61616?clusterClientsConnectionParams="useCompression=true"
> * tcp://somebrokerB:61616?clusterClientsConnectionParams="useCompression=true"
> * tcp://somebrokerC:61616?clusterClientsConnectionParams="useCompression=true"
> Thanks,
> Scott ES
> http://fusesource.com
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
