0 Replies Latest reply on Jan 16, 2014 10:04 AM by s.horn

    java.lang.IllegalStateException: EJBCLIENT000025: No EJB receiver available for handling [appName, moduleName, distinctName] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@785c


      Hello community,


      i am running into this exception when i trying to use scoped context lookup for our application.


      It always occurs when i try to invoke a method of an Bean which is not created directly by remote lookup, but is fetched over an other bean.

      With other words we have an EJB(A) which is returning an other EJB (B).


      While debugging i recognized that the EJB (B) uses an other EJBClientContext than EJB (A).

      It seems use the default context, resulting in EBCLIENT000025: No EJB receiver available for handling.


      When i use the following construct - I guess it overrides the default EJBClientContext -  every thing works fine:


      EJBClientConfiguration clientconfiguration = new PropertiesBasedEJBClientConfiguration(props);
      ContextSelector<EJBClientContext> ejbContextSelector = new ConfigBasedEJBClientContextSelector(clientconfiguration);


      Any Ideas howto pass the EJBClientContext (and the contained EJBReceivers) to EJB(B)?


      Is this a Bug in Scoped context lookup?


      I am running JBoss-eap-6.1.


      Thanks in advance