1 Reply Latest reply on Feb 9, 2017 5:22 AM by Anup Dey

    EJBCLIENT000025: No EJB receiver available for handling XXX combination for invocation context

    bug menot Newbie

      I recently switched from JBoss EAP 6.4.0 to 7.0.0. The server starts up fine, but when I run the client, I'm stuck with this error message:

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

      My connection settings are as follows:




      I can connect to the server using telnet:


      telnet localhost 8080


      My colleagues (same setup, but different IDE) can run the client without any problems.


      What am I doing wrong? What else can I check?

        • 1. Re: EJBCLIENT000025: No EJB receiver available for handling XXX combination for invocation context
          Anup Dey Expert

          It can have several issues :


          - connection: Connection broken

          - security : user/pass invalid

          - EJB missing: connected, but ejb is not there

          - SSL



          The EJBClientContext will keep all available receiver in a Map where the servers name is the key.

          If there is more than one server with the same name these entries will be lost.


          If it is inside of a server instance this instance will be preferred and all other instances with the same server name are hidden.

          In this case no EJB will be accessible which is only available on such server.


          There are three situation under which the EJBCLIENT000025 is thrown

          1] Connection broken

          2] user/pass invalid

          3] connected, but ejb is not there


          JBoss maintains a persistent connection to the other server, so when the client sees this message it means there is no connection to a server that has the ejb you are trying to call, so a message will be logged when the connection fails to the other server.


          This error below given it happens just after you setup the scoped context ejb connection likely means the connection failed, so the logging earlier would indicate the cause which is typically wrong host/port, user/pass, unable to connect to the host, ...



          check the outbound-connection

          check the user and password at destination server (NOTE: need to be EAP application user, not management user)

          check the secret value at target server

          check that there are no extra spaces left after the specifying a property in jboss-ejb-client.properties file.

          enable org.jboss.ejb.client and org.jboss.remoting for TRACE logging to see detailed messages for the invocation at client side.


          See links[1] and [2].


          [1] https://docs.jboss.org/author/display/AS71/EJB+invocations+from+a+remote+client+using+JNDI

          [2] https://docs.jboss.org/author/display/AS71/EJB+invocations+from+a+remote+server+instance