Status: New
Owner: ----
Labels: Priority-Medium

New issue 124 by [email protected]: RoundRobinLoadBalancerElector is not thread safe
http://code.google.com/p/jain-sip/issues/detail?id=124

What steps will reproduce the problem?
1. Configure JainSlee SIP-RA with two SIPLDB nodes, wheras one should be unavailable
2. Send a reasonable Number of CPS to the system using any SIP Testservice

What is the expected output? What do you see instead?
1. Expected: All Calls should be routed to the active LDB
2. Real: Sporadically Calls are routed to the inactive LDB


What version of the product are you using? On what operating system?
2.7.0 JainSlee Release - which is using Jain-SIP-HA 1.3.0

Please provide any additional information below.
The issue was already posted in mobicents-public on 2013/08/06

Solution:
The selection of the unavailable LDB-Node can be tracked down to RoundRobinLoadBalancerElector. Under a significant number of parallel Threads getNextIndex() may repeatedly return one and the same unavailable Node Index.

Attached RoundRobinAvailableLoadBalancerElector avoids this by checking availablity already in getNextIndex() method. RoundRobinLoadBalancerElectorTest (adoption of original Testclass from jain-sip-jboss5 project) also attached.

It has to be decided if RoundRobinAvailableLoadBalancerElector will replace RoundRobinLoadBalancerElector, or if it will exist as parallel implementation (Elector-Implementation can be configured within SIP-RA anyway)


Attachments:
        RoundRobinLoadBalancerElectorTest.java  15.2 KB
        RoundRobinAvailableLoadBalancerElector.java  3.1 KB

--
You received this message because this project is configured to send all issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

--

--- You received this message because you are subscribed to the Google Groups "mobicents-all-issues-changes" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to