[
https://issues.jboss.org/browse/AS7-3492?page=com.atlassian.jira.plugin.s...
]
Radoslav Husar commented on AS7-3492:
-------------------------------------
I agree with Brian, seems like every users wants this not realizing that the network
overhead just kills performance.
So how do you want to go around doing this Jaikiran? What config options will the users
have? Is it necessary though for final? Is it correct to assume that CDI has virtually
nothing to do with this regarding failover (HA)?
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