activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Tully (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-3707) Dynamic Failover Client Connection Params Broker Side Attribute
Date Thu, 09 Feb 2012 11:29:00 GMT

    [ https://issues.apache.org/jira/browse/AMQ-3707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13204454#comment-13204454
] 

Gary Tully commented on AMQ-3707:
---------------------------------

it may be better to leave these options as part of the failover transport as they are client
specific options.
Something like this exists for discovered transports{{discovery:(multicast://default)?initialReconnectDelay=100&discovered.closeAsync=false"}}.
see: https://issues.apache.org/jira/browse/AMQ-3222

I think it makes sense to use the same mechanism for failover updates as this is a form of
discovery.
                
> 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.6.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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message