[
https://issues.jboss.org/browse/AS7-3492?page=com.atlassian.jira.plugin.s...
]
Jason Greene updated AS7-3492:
------------------------------
Fix Version/s: 7.1.2.Final
(was: 7.1.1.Final)
This issue is being relocated to 7.1.2 so that 7.1.1 only contains criticals, blockers,
and EAP LA issues (which are probably not yet at the right status, or need an extra triage
pass).
If these issues are completed in a 7.1.1 timeframe please change the fix version. Although
if you forget I will bulk correct.
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.2.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