activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Felix Ehm (JIRA)" <j...@apache.org>
Subject [jira] Updated: (AMQ-2632) Update client connections with information about a cluster of networked brokers
Date Mon, 10 Jan 2011 14:35:47 GMT

     [ https://issues.apache.org/jira/browse/AMQ-2632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Felix Ehm updated AMQ-2632:
---------------------------

    Comment: was deleted

(was: Thanks for this very useful feature!

However, it is not clear to me why I have the switch on the transport configuration (updateClusterClients="true|false")
which is happily ignored? 

I've tested it with the two example dynamic broker configuration files shipped in 5.4.1 package.
The clients are always updated about a cluster member even when setting updateClusterClients=false
or using the broker filter:
{code:xml}
dynamic-broker-1:
<!-- this is the only broker the clients should connect to.
<transportConnectors>
   <transportConnector name="openwire" 
        uri="tcp://0.0.0.0:61616" 
        discoveryUri="multicast://default" 
        <!-- no update od clients -->
        updateClusterClients="false" 
        <!-- to be very sure, just include this broker as cluster member for client update
-->
        updateClusterFilter="dynamic-broker-1"/>
</transportConnectors>
{code}
{code:xml}
dynamic-broker-2:
<!-- this broker shouldn't be seen by the clients at all. However, it should be in the
same cluster as broker-1 -->
<transportConnectors>
            <transportConnector name="openwire" uri="tcp://0.0.0.0:61618" discoveryUri="multicast://default"
/>
</transportConnectors>
{code}

btw: changing the connection url on the client side is unfortunately not an option for us.


Is this mechanism going to be changed/fixed in the next version ?
)

> Update client connections with information about a cluster of networked brokers
> -------------------------------------------------------------------------------
>
>                 Key: AMQ-2632
>                 URL: https://issues.apache.org/jira/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.


Mime
View raw message