Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (athena.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;
  h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type;
  b=YaifdRdSYEXYWWWmSR5YVJV6fnE/jmodP4LFeMhlbTl+5y5Rdc6tzNi/7CEmHpzJ+UVgPI6SX5n6yWd7w8tzFUS7lnN6hJ2cN6eDEjycRHwSnG++e3A20L5jcDBNi/uNKteLAzljE+6MJpyXDJgGNi/RPmUHvfM46/yoPGonfHk=;
Message-ID: <687437.92864.qm@web121609.mail.ne1.yahoo.com>
References: <397685.19709.qm@web121605.mail.ne1.yahoo.com>
Date: Fri, 25 Feb 2011 14:22:04 -0800 (PST)
From: Joe Smith <joesmithcomm@yahoo.com>
Subject: Re: Connection Re-balance Question
To: users@activemq.apache.org
In-Reply-To: <397685.19709.qm@web121605.mail.ne1.yahoo.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="0-482840212-1298672524=:92864"

--0-482840212-1298672524=:92864
Content-Type: multipart/alternative; boundary="0-1668219658-1298672524=:92864"

--0-1668219658-1298672524=:92864
Content-Type: text/plain; charset=us-ascii

Attachment.


________________________________
From: Joe Smith <joesmithcomm@yahoo.com>
To: users@activemq.apache.org
Sent: Fri, February 25, 2011 5:14:51 PM
Subject: Connection Re-balance Question

Hi, 

I'm using the 5.4.x transport's updateClusterClients="true" 
rebalanceClusterClients="true"  options. 


It works fine as a broker is added to the cluster - the existing connections are 

rebalanced. 


When a broker that's already in the cluster when down, the connections failed 
over successfully to the other broker (clients are using failover://).  However, 

when I bring up the failed broker, the connections on the other broker are not 
re-balanced.

My questions are:

1. Does connection re-balancing work in this scenario - where a known broker in 
the cluster comes back on line after a crash?

2. What criteria need to be met before re-balance would occur other than when a 
NEW (vs. existing) broker is added to the cluster?  E.g. we have only 24 client 
connections, is that too low?

We tried both 5.4.1 and 5.4.2. Linux. JVM is 1.6. 

Thanks for the help. 


--0-1668219658-1298672524=:92864
Content-Type: text/html; charset=us-ascii

<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:times new roman,new york,times,serif;font-size:12pt">Attachment.<br><div><br></div><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;"><br><div style="font-family: arial,helvetica,sans-serif; font-size: 13px;"><font face="Tahoma" size="2"><hr size="1"><b><span style="font-weight: bold;">From:</span></b> Joe Smith &lt;joesmithcomm@yahoo.com&gt;<br><b><span style="font-weight: bold;">To:</span></b> users@activemq.apache.org<br><b><span style="font-weight: bold;">Sent:</span></b> Fri, February 25, 2011 5:14:51 PM<br><b><span style="font-weight: bold;">Subject:</span></b> Connection Re-balance Question<br></font><br>
Hi, <br><br>I'm using the 5.4.x transport's updateClusterClients="true" <br>rebalanceClusterClients="true"&nbsp; options. <br><br><br>It works fine as a broker is added to the cluster - the existing connections are <br>rebalanced. <br><br><br>When a broker that's already in the cluster when down, the connections failed <br>over successfully to the other broker (clients are using failover://).&nbsp; However, <br>when I bring up the failed broker, the connections on the other broker are not <br>re-balanced.<br><br>My questions are:<br><br>1. Does connection re-balancing work in this scenario - where a known broker in <br>the cluster comes back on line after a crash?<br><br>2. What criteria need to be met before re-balance would occur other than when a <br>NEW (vs. existing) broker is added to the cluster?&nbsp; E.g. we have only 24 client <br>connections, is that too low?<br><br>We tried both 5.4.1 and 5.4.2. Linux. JVM is 1.6. <br><br>Thanks for the help.
 <br><br><br>&nbsp; &nbsp; &nbsp; </div></div>
</div><br>

      </body></html>
--0-1668219658-1298672524=:92864--

--0-482840212-1298672524=:92864--