[jboss-jira] [JBoss JIRA] (AS7-5416) Cannot invoke remote EJB3 from secondery top level deployement

[Thijs Eggen (JIRA)]

Thijs Eggen created AS7-5416:
--------------------------------

             Summary: Cannot invoke remote EJB3 from secondery top level deployement
                 Key: AS7-5416
                 URL: https://issues.jboss.org/browse/AS7-5416
             Project: Application Server 7
          Issue Type: Bug
          Components: EJB
    Affects Versions: 7.1.1.Final
            Reporter: Thijs Eggen
            Assignee: jaikiran pai


I've got a local jboss setup with 2 top level deployments
- myEar.ear
  - META-INF/jboss-ejb-client.xml
- myWar.war
  - WEB-INF/jboss-ejb-client.xml

A thirth EJB (serviceEJB) is running on a remote service. When I try to lookup my remote service from my war is is pickup nice and smooth but I can't lookup the serviceEJB from the ear (myEar). Resulting in a 'No EJB receiver available for handling [appName:referentie-component-ear,modulename:referentie-component-ejb,distinctname:]

When starting my local jboss setup the jboss-ejb-client.xml the remote connection is setup.
15:25:23,758 INFO  [org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver] (MSC service thread 1-1) Successful version handshake completed for receiver context EJBReceiverContext{clientContext=org.jboss.ejb.client.EJBClientContext at 6f4370c1, receiver=Remoting connection EJB receiver [connection=Remoting connection <1d6c023d>,channel=jboss.ejb,nodename=dmpMO:server-dmp-mo]} on channel Channel ID baa352ab (outbound) of Remoting connection 4a43dc54 to DMP-MO-FSC2/161.89.55.159:4447

But when my webapp calls MyEar which calls the ServiceEJB 'No EJB receiver available' error. The remote connection is setup according: https://docs.jboss.org/author/display/AS71/EJB+invocations+from+a+remote+server+instance

It looks like only one (the war) top level deployment can setup a remote connection. 

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