Follow up to: https://bugzilla.redhat.com/show_bug.cgi?id=1350355 Prior to changes, when a remote external EJB client tried to invoke an EJB such as a SLSB which was in an app with a Singleton which was not yet finished PostConstruct, the remote client would get an EJBCLIENT000025. After the bug fixes it now is not getting the exception. We need to keep it consistent since it was working that way for the previous 6.x releases: java.lang.IllegalStateException: EJBCLIENT000025: No EJB receiver available for handling [appName:, moduleName:ejb-client, distinctName:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@2473d930
https://github.com/jbossas/jboss-eap/pull/2829
Verified with EAP 6.4.11.CP.CR1
Retroactively bulk-closing issues from released EAP 6.4 cummulative patches.