In the issue WFLY-21094, a number of key ejb3 subsystem services are started ON_DEMAND so that services are only started in the subsystem when they are required (i.e. when the server receives a deployment containing EJBs). There is little point starting such services when deployments do not exist.

One side effect of these changes, however, is that when the EJBRemoteConectorService is not started, invocations which target EJBs and which arrive when no EJBs are deployed will cause exceptions, instead of returning the standard NoSuchEJBException to the client.

For example, if the case of EJB/Remoting, the following error will arise if no EJB deployment is available on the server and the server received an EJB invocation request:

org.jboss.ejb.client.RequestSendFailedException: org.jboss.remoting3.ServiceOpenException: Unknown service name jboss.ejb@remote+http://127.0.0.1:8080
    at org.jboss.ejb.protocol.remote.RemoteEJBReceiver$1.lambda$handleDone$0(RemoteEJBReceiver.java:87)
    at org.xnio.AbstractIoFuture$NotifierRunnable.run(AbstractIoFuture.java:856)
    at org.xnio.IoUtils$2.execute(IoUtils.java:71)
    at org.xnio.AbstractIoFuture.runNotifier(AbstractIoFuture.java:829)

The aim of this issue is to find a way to cleanly respond to such an invocation in a way which is consistent with legacy behavior.