[jboss-jira] [JBoss JIRA] (WFLY-3438) Eliminate use of optional dependencies for LocalEJBReceiver

[Richard Achmatowicz (JIRA)]

Richard Achmatowicz created WFLY-3438:
-----------------------------------------

             Summary: Eliminate use of optional dependencies for LocalEJBReceiver
                 Key: WFLY-3438
                 URL: https://issues.jboss.org/browse/WFLY-3438
             Project: WildFly
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: EJB
    Affects Versions: 8.0.0.Final, 9.0.0.Alpha1
            Reporter: Richard Achmatowicz
            Assignee: Richard Achmatowicz
             Fix For: 9.0.0.CR1


This issue was initially raised on stackoverflow (see below).

When the EJB subsystem starts, it starts instances of LocalEJBReceiver which have optional dependencies on the Remoting Endpoint as well as the EJBRemotingConnectorService. I assume that these were marked as optional as remote invocations on EJBs is not required by the spec for the web profile. 

As stated in the forum post, the issue is that the LocalEJBReceiver gets started before its dependency EJBRemotingConnectorService and so the dependency does not get resolved correctly - this effectively turns off the LocalEJBReceiver's ability to add cluster nodes to cluster contexts for the clusters it belongs to.

This results in the exception
.java.lang.IllegalStateException: EJBCLIENT000029: No cluster context available for cluster named ejb





--
This message was sent by Atlassian JIRA
(v6.2.3#6260)