EAP 6.2.0.ER7. The command mvn exec:exec in quickstart ejb-security-interceptors fails with the following exception: Exception in thread "main" java.lang.IllegalStateException: EJBCLIENT000025: No EJB receiver available for handling [appName:, moduleName:jboss-as-ejb-security-interceptors, distinctName:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@12ad972d at org.jboss.ejb.client.EJBClientContext.requireEJBReceiver(EJBClientContext.java:729) at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:116) at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:183) at org.jboss.ejb.client.EJBInvocationHandler.sendRequestWithPossibleRetries(EJBInvocationHandler.java:253) at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:198) at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:181) at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:144) at $Proxy0.getSecurityInformation(Unknown Source) at org.jboss.as.quickstarts.ejb_security_interceptors.RemoteClient.makeCalls(RemoteClient.java:135) at org.jboss.as.quickstarts.ejb_security_interceptors.RemoteClient.performTestingSecurityContext(RemoteClient.java:62) at org.jboss.as.quickstarts.ejb_security_interceptors.RemoteClient.main(RemoteClient.java:170) This is caused by the jar name change (from "jboss-as-ejb-security-interceptors" to "jboss-ejb-security-interceptors"), however the EJB calls in the sources still use the old name. The very same issue was also seen in the quickstart cluster-ha-singleton: https://bugzilla.redhat.com/show_bug.cgi?id=1028517.
Fixed in commit: https://github.com/jboss-developer/jboss-eap-quickstarts/commit/7ead9504f39d44bb9e5e163fe03ac96908d20a29
Verified using EAP 6.2.0.CR1 bits.