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 EJB3RemoteHTTPService 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, in the case of EJB/HTTP, an HTTP response code of 404 will be returned if the service has not started, as the purpose of the EJB3RemteHTTPService is to install Undertow handlers for the HttpInvoker which handle context paths of the form:

http://<host>:<port>/wildfly-services/ejb/{invoke, create, cancel, discover}

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.