[jboss-jira] [JBoss JIRA] (AS7-4862) Remote EJB cluster view propagation or SFSB load balancing broken

[jaikiran pai (JIRA)]

    [ https://issues.jboss.org/browse/AS7-4862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12699188#comment-12699188 ] 

jaikiran pai commented on AS7-4862:
-----------------------------------

The tone in one of my previous replies wasn't right. Just to be clear - I'm willing to consider providing a different deployment node selector implementation from within the EJB client API project, if there are clear requirements on its algorithm for node selection and if it's useful enough for client applications. 

The part I don't agree with, is the claim that this is a bug and the functionality is broken. It works as advertised and even allows client applications to configure they own implementation. 
                
> Remote EJB cluster view propagation or SFSB load balancing broken
> -----------------------------------------------------------------
>
>                 Key: AS7-4862
>                 URL: https://issues.jboss.org/browse/AS7-4862
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: Clustering, EJB
>    Affects Versions: 7.1.2.Final (EAP)
>            Reporter: Radoslav Husar
>            Assignee: Radoslav Husar
>             Fix For: 7.1.3.Final (EAP)
>
>
> Looking at the load-balancing again, it seems still wrong. Checking the logs, servers were started *and cluster was formed* ~10 seconds prior to starting the client and load-balancing was roughly: 
> * node perf18: ~50% of sessions
> * node perf19: 0
> * node perf20: 0
> * node perf21: ~50% of sessions
> I let all the session to be created in one minute (not all at once).
> The nodes were also specified in the properties.
> {noformat}
> node perf18
> [JBossINF] 07:01:53,991 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (CacheService lifecycle - 1) ISPN000094: Received new cluster view: [perf19/ejb|3] [perf19/ejb, perf21/ejb, perf20/ejb, perf18/ejb]
> node perf19
> [JBossINF] 07:01:53,781 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-19,null) ISPN000094: Received new cluster view: [perf19/ejb|3] [perf19/ejb, perf21/ejb, perf20/ejb, perf18/ejb]
> node perf20
> [JBossINF] 07:01:53,781 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-14,null) ISPN000094: Received new cluster view: [perf19/ejb|3] [perf19/ejb, perf21/ejb, perf20/ejb, perf18/ejb]
> node perf21
> [JBossINF] 07:01:53,780 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-12,null) ISPN000094: Received new cluster view: [perf19/ejb|3] [perf19/ejb, perf21/ejb, perf20/ejb, perf18/ejb]
> controller node
> 2012/05/22 07:02:02:932 EDT [DEBUG][TestController] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Setting thread count: 2000, was: 0
> 2012/05/22 07:02:53:731 EDT [DEBUG][TestController] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - All runners (2000) started in 50799 milliseconds
> {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira