[jboss-jira] [JBoss JIRA] (AS7-3492) Server side invocations on a clustered stateful bean end up being handled on the same local node

[Brian Stansberry (JIRA)]

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

Brian Stansberry commented on AS7-3492:
---------------------------------------

The intent was to route locally, as the performance of that is much better in the large majority of use cases.

Some people did want to load balance the EJB calls. It was a pretty frequent issue on the forums where EJB2 users would ask about how to configure the EJB2 thing I mentioned. My impression is most of the time the discussion led the users to realize they didn't really want to do that. But, not all the time. So, being able to configure things such that calls are load balanced is a legit feature request.

The main thing IMO is it needs to be easy for users to end up with the most performant behavior. They should have to go out of their way to end up with calls going remote.

This may be something of a non-issue if the concern I have can be solved just by saying "inject a local view if you want to stay in-vm". Which perhaps is what you're plan is anyway!

Note that EJB3 HA != load balanced EJB3/Remoting calls. SFSB replication needs to work even if all access to the bean is in-vm via servlets. That's because the HTTP session is replicated and calls are load balanced at the HTTP level. If the HTTP session fails over, the SFSB state needs to be there.
                
> Server side invocations on a clustered stateful bean end up being handled on the same local node
> ------------------------------------------------------------------------------------------------
>
>                 Key: AS7-3492
>                 URL: https://issues.jboss.org/browse/AS7-3492
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: Clustering, EJB
>    Affects Versions: 7.1.0.CR1b
>            Reporter: jaikiran pai
>            Assignee: jaikiran pai
>             Fix For: 7.1.0.Final
>
>
> Currently, if a stateful bean is @Cluster(ed) and an invocation on it is done from within the same server, invocations on that bean are always handled by the LocalEJBReceiver even if the cluster has multiple others nodes hosting that stateful bean.
> The LocalEjbReceiver currently receives the cluster topology but doesn't create (remote) EJB receviers out of it for the client context. The missing piece is configurations that need to be passed for creating the remote EJB receivers.  

--
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