[jboss-jira] [JBoss JIRA] (AS7-3492) Failover of clustered bean invocations might not happen if the client itself is a server instance and the client server had a local deployment handling the invocation

Brian Stansberry (JIRA) jira-events at lists.jboss.org
Wed Apr 25 11:53:17 EDT 2012


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

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

The use case you describe is valid and what you describe sounds correct. The intended behavior in AS < 7 was not to disable failover, it was to route the call locally if possible. I would consider disabling failover altogether to be a regression.

I mentioned before that perhaps "the concern (about the cost of going remote) can be solved just by saying "inject a local view if you want to stay in-vm"." So if getting the affinities to work properly for this case is a problem, keep that in mind.
                
> Failover of clustered bean invocations might not happen if the client itself is a server instance and the client server had a local deployment handling the invocation
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 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.2.Final-redhat1
>
>
> 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

        


More information about the jboss-jira mailing list