Jboss EAP-6.3 remote stateless bean invocation failed on other Jboss EAP-6.3 instance

[jbosstcsbala]

Dear All,

     Currently, I'm working on EJB with web client, I've two EAP instance; one for EJB server deployment and another for web application with EJB client calling. I have configured the standalone EJB client calling, it's working fine, but from web I'm getting bellow error, Can you please any one help me.

Error Log:

11:33:21,283 ERROR [stderr] (ServerService Thread Pool -- 89) java.lang.IllegalStateException: EJBCLIENT000031: No receiver associated with invocation

11:33:21,283 ERROR [stderr] (ServerService Thread Pool -- 89)     at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:179)

11:33:21,283 ERROR [stderr] (ServerService Thread Pool -- 89)     at org.jboss.ejb.client.EJBInvocationHandler.sendRequestWithPossibleRetries(EJBInvocationHandler.java:253)

11:33:21,283 ERROR [stderr] (ServerService Thread Pool -- 89)     at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:198)

11:33:21,283 ERROR [stderr] (ServerService Thread Pool -- 89)     at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:181)

11:33:21,283 ERROR [stderr] (ServerService Thread Pool -- 89)     at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:144)

11:33:21,301 ERROR [stderr] (ServerService Thread Pool -- 89)     at $Proxy14.initialize(Unknown Source)

11:33:21,301 ERROR [stderr] (ServerService Thread Pool -- 89)     at com.test.ServiceCaller.getSessionManager(ServiceCaller.java:316)

11:33:21,301 ERROR [stderr] (ServerService Thread Pool -- 89)     at com.test.ServiceCaller.initializeEJB(ServiceCaller.java:487)

11:33:21,301 ERROR [stderr] (ServerService Thread Pool -- 89)     at com.test.ServiceCaller.<init>(ServiceCaller.java:125)

11:33:21,316 ERROR [stderr] (ServerService Thread Pool -- 89)     at com.test.ServiceCaller.<init>(ServiceCaller.java:94)

11:33:21,316 ERROR [stderr] (ServerService Thread Pool -- 89)     at com.test.Config.init(Config.java:355)

11:33:21,316 ERROR [stderr] (ServerService Thread Pool -- 89)     at com.test.ConfigServlet.init(ConfigServlet.java:57)

11:33:21,316 ERROR [stderr] (ServerService Thread Pool -- 89)     at javax.servlet.GenericServlet.init(GenericServlet.java:242)

11:33:21,316 ERROR [stderr] (ServerService Thread Pool -- 89)     at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1194)

11:33:21,316 ERROR [stderr] (ServerService Thread Pool -- 89)     at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1100)

11:33:21,316 ERROR [stderr] (ServerService Thread Pool -- 89)     at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3591)

11:33:21,316 ERROR [stderr] (ServerService Thread Pool -- 89)     at org.apache.catalina.core.StandardContext.start(StandardContext.java:3798)

11:33:21,316 ERROR [stderr] (ServerService Thread Pool -- 89)     at org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:161)

11:33:21,316 ERROR [stderr] (ServerService Thread Pool -- 89)     at org.jboss.as.web.deployment.WebDeploymentService.access$000(WebDeploymentService.java:59)

11:33:21,316 ERROR [stderr] (ServerService Thread Pool -- 89)     at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:94)

11:33:21,316 ERROR [stderr] (ServerService Thread Pool -- 89)     at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)

11:33:21,316 ERROR [stderr] (ServerService Thread Pool -- 89)     at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)

11:33:21,316 ERROR [stderr] (ServerService Thread Pool -- 89)     at java.util.concurrent.FutureTask.run(FutureTask.java:138)

11:33:21,316 ERROR [stderr] (ServerService Thread Pool -- 89)     at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)

11:33:21,316 ERROR [stderr] (ServerService Thread Pool -- 89)     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)

11:33:21,316 ERROR [stderr] (ServerService Thread Pool -- 89)     at java.lang.Thread.run(Thread.java:662)

11:33:21,316 ERROR [stderr] (ServerService Thread Pool -- 89)     at org.jboss.threads.JBossThread.run(JBossThread.java:122)

Please find the reference link : http://www.mastertheboss.com/jboss-server/jboss-as-7/how-to-call-ejbs-from-another-jboss-as-7-instance

Thanks,

Bala.

[wdfink]

Seems a configuration problem.

Could you show how you start both servers and the relevant part of the web-server standalone.xml, the invocation code and the logfile from the ejb side where you see the deployment names of the target EJB?

Also you might have a look to the EAP quickstarts (you can download it for your version if you have a subscription) the ejb-multi-server quickstart contains a web application which use EJB's on a different server.

[aleques]

Did you update with patches? Now I have this problem after update.

My env:

JBossMachineA with ModuleX and DeployedEarX

JBossMachineB with DeployedEarY

JBoss EAP 6.4.0 original (without patch)

EjbRemoteCall from DeployedEarX to DeployedEarY ====> OK!

EjbRemoteCall from ModuleX to DeployedEarY ====> OK!

JBoss EAP 6.4.0 After Patch 6.4.5

EjbRemoteCall from DeployedEarX to DeployedEarY ====> OK!

EjbRemoteCall from ModuleX to DeployedEarY ====> FAIL! ("EJBCLIENT000031: No receiver associated with invocation")

I got a solution inside my ModuleX (LoginModule)

change this

<login-module name="app" code="br.com.teste.App" flag="required" module="br.com.teste"/>

for this

<login-module name="app" code="br.com.teste.App" flag="required"/>

This worked for me, but I got this error again in another scenario.... I'm almost giving up of this update patch.

[xibo_flair]

I have encountered the same error.

I have 2 client applications making remote EJB calls to the server. One is working and the other is not. I have turned on the scoped ejb context for both clients, i.e., prop.put("org.jboss.ejb.client.scoped.context", "true");

The one that fails with the error is a java swing application. When I set the scoped context to false, the error is gone. But I do need to set this property to true because the EJB context can be closed properly only if this property is set to true.