java.lang.IllegalStateException: EJBCLIENT000025: No EJB receiver available for handling

Triscana

unread,

Feb 5, 2021, 7:24:41 AM2/5/21

to WildFly

Hey everyone,

We are working migrating a application from WF9 to WF20.

At the moment we are facing a issue with a remote client in order to access a EJB, as the error above.

We followed the WF20 documentation here https://docs.wildfly.org/20/Developer_Guide.html#EJB_invocations_from_a_remote_client_using_JNDI and still the same issue.

I've enabled the org.jboss.ejb.client and org.jboss.remoting Logs, as DEBUG, on the server-side but no information is catch.

Any Help here.. is really appreciated.

Thanks in advance.

Josh Fisher

unread,

Feb 5, 2021, 12:20:12 PM2/5/21

to WildFly

You probably will want to look at the client-side logs and error information.

In my experience, these errors are usually a sign of the client not being able to make the call for one of these reasons:

Application/EJB is not deployed
Server is down or not reachable
Traffic blocked by firewall or other networking issues
Client is not configured properly, such as incorrect java.naming.provider.url property value

I don't think you will see much or anything in server-side logs, since in most of these cases the call does not reach the server.

I hope that helps.

Thales Horta

unread,

Feb 5, 2021, 12:58:04 PM2/5/21

to WildFly

Hi Josh,

Many thanks for your time here, it's really helpful.

Based on the possible reasons, I did check must of them, my main concern right now is the client is not configured properly or EJB not deployed.

In order to avoid many changes from Development, i'd like to see which EJB are being requested from the Server-Side.. do you know if is that possible?

Thanks again for your help here.

Cheers.

TpH

Wolfgang

unread,

Feb 5, 2021, 4:59:53 PM2/5/21

to WildFly

Hi,

what is your "Context.INITIAL_CONTEXT_FACTORY" and "Context.PROVIDER_URL"? The doc is outdated since WildFly 11 (https://issues.redhat.com/browse/WFLY-9459), now you have to use:

env.put(Context.INITIAL_CONTEXT_FACTORY, "org.wildfly.naming.client.WildFlyInitialContextFactory");

env.put(Context.PROVIDER_URL,"remote+http://localhost:8080");

Hope this helps

Wolfgang

Thales Horta

unread,

Feb 8, 2021, 9:38:53 AM2/8/21

to WildFly

Hi Wolfgang, Thanks for the answer.

Actually is already using env.put(Context.INITIAL_CONTEXT_FACTORY, "org.wildfly.naming.client.WildFlyInitialContextFactory");

For the Provider_URL is a remote server so, we're using the IP and the port

Context.PROVIDER_URL = remote+http://192.168.131.202:8183

It's a JNLP standalone client, all the jar libs has been update, but the message still there.