It can have several issues :
- connection: Connection broken
- security : user/pass invalid
- EJB missing: connected, but ejb is not there
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 and .