[jboss-remoting-issues] [JBoss JIRA] Updated: (JBREM-1105) DefaultLoadBalancer doesn't use all available server (if there are x servers available it uses x-1 of these)
Ron Sigal (JIRA)
jira-events at lists.jboss.org
Mon May 11 23:59:46 EDT 2009
[ https://jira.jboss.org/jira/browse/JBREM-1105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ron Sigal updated JBREM-1105:
-----------------------------
Fix Version/s: 2.2.2.SP13
(was: 2.2.2.SP12)
(was: 2.5.2 (Flounder))
Pushed to 2.2.2.SP13.
> DefaultLoadBalancer doesn't use all available server (if there are x servers available it uses x-1 of these)
> ------------------------------------------------------------------------------------------------------------
>
> Key: JBREM-1105
> URL: https://jira.jboss.org/jira/browse/JBREM-1105
> Project: JBoss Remoting
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: transporter
> Affects Versions: 2.5.0.SP2 (Flounder) , 2.2.2.SP11
> Environment: JBoss EAP 4.3.0, Windows XP, Java 1.6.0_11
> Reporter: Mikael Thorman
> Assignee: Ron Sigal
> Fix For: 2.2.2.SP13
>
>
> Invalid use of the Random nextInt function in class: org.jboss.remoting.transporter.DefaultLoadBalancer function: selectServer
> Current code:
> index = new Random().nextInt(size - 1);
> Should be:
> index = new Random().nextInt(size);
> tested current code with 2 servers and it always chooses the first one until this is shut, first after this it uses the second one.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-remoting-issues
mailing list