activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <>
Subject [jira] [Resolved] (AMQ-3707) Dynamic Failover Client Connection Params Broker Side Attribute
Date Tue, 18 Dec 2012 21:24:13 GMT


Timothy Bish resolved AMQ-3707.

    Resolution: Fixed

Fixed in svn rev: 1428655

The transport connector can now have a clusterClientUriQuery value set which will be added
to the published connect string.  Currently the activemq openwire client will only apply transport
and wireformat level options as the ConnectionFactory parses out the jms.* properties of the
client specified URI.  If you need to set those then we'd need to think about how to implement
that dynamically and safely when a failover transport reconnect uses one of those cluster
updated URI's, open a new issue for that if its really needed. 
> Dynamic Failover Client Connection Params Broker Side Attribute
> ---------------------------------------------------------------
>                 Key: AMQ-3707
>                 URL:
>             Project: ActiveMQ
>          Issue Type: New Feature
>          Components: Broker
>            Reporter: Scott England-Sullivan
>             Fix For: 5.8.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
> 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

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:

View raw message