activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "clebert suconic (JIRA)" <>
Subject [jira] [Closed] (ARTEMIS-684) Randoms are not equally distributed, causing Load balance to fail over multiple VMs
Date Wed, 16 Nov 2016 14:43:59 GMT


clebert suconic closed ARTEMIS-684.
       Resolution: Fixed
    Fix Version/s: 1.4.0

> Randoms are not equally distributed, causing Load balance to fail over multiple VMs
> -----------------------------------------------------------------------------------
>                 Key: ARTEMIS-684
>                 URL:
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>    Affects Versions: 1.4.0
>            Reporter: Chen Maoqian
>            Priority: Critical
>             Fix For: 1.4.0
>         Attachments:
> When we use each Connection Factory create a single Connection, Client connection are
not balanced across cluster with any load balancing policy.
> you can modify the cluster-static-discovery example to reproducer the solution.
> *Scenario*
> There two nodes in cluster. Nodes in cluster are connected and both nodes have same jms
destinations and connection factory defined like the following one
> {noformat}
>  <connection-factory name="RemoteConnectionFactory" connectors="http-connector" entries="java:jboss/exported/jms/RemoteConnectionFactory"
ha="true" connection-ttl="120000" call-timeout="60000" block-on-acknowledge="true" retry-interval="1000"
reconnect-attempts="-1" connection-load-balancing-policy-class-name="org.apache.activemq.artemis.api.core.client.loadbalance.RandomConnectionLoadBalancingPolicy"/>
> {noformat}
> There are clients connecting to cluster. With _RandomConnectionLoadBalancingPolicy_,
I would expect that connections are randomly distributed among the nodes in cluster. However,
when I list connections on both nodes (/subsystem=messaging-activemq/server=default:list-connection-ids),
all connections are on one server. 
> Method {{private TransportConfiguration selectConnector()}} in class {{ServerLocatorImpl}}
checks whether the {{topologyArray}} is null and makes decision between choosing connector
to other node in topology or initial connector of connection factory. In method {{private
TransportConfiguration selectConnector()}}  {{topologyArray}} is still null, so clients make
connection using initial connector. It seems like {{topologyArray}} is only updated during
{{notifyNodeUp/Down}} methods.
> Could you please explain how is this client connection balancing supposed to work?

This message was sent by Atlassian JIRA

View raw message