Could this be included in the 6.1.1 release ?

Created a PR for this:

https://github.com/jbossas/jboss-eap/pull/217

Tom or someone from the support team, I would like someone from the team to test this fix before asking the customer to try it, please. I did not have the necessary setup or application to give that fix a try. If you had this reproducable locally for you, then please test out the fix and see if it really fixes it (it should).

No problem I can test it since I still have the test case. Let me know where i can find the build.

Hi Tom, the fix has been merged to WildFly upstream and is available from here https://community.jboss.org/thread/224262.

Thank you for this pointer. I have managed to build WildFly Alpha 3. Do you think that would be enough if I run my test case with that build?

Yes, that much should be fine.

Running the test case results in this messages on the client side:
[INFO] --- exec-maven-plugin:1.2.1:java (default-cli) @ jboss-as-ejb-multi-server-client ---
[WARNING]
java.lang.reflect.InvocationTargetException
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:297)
	at java.lang.Thread.run(Thread.java:724)
Caused by: java.lang.IllegalStateException: EJBCLIENT000025: No EJB receiver available for handling [appName:appmain, moduleName:ejb, distinctName:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@55c915a5
	at org.jboss.ejb.client.EJBClientContext.requireEJBReceiver(EJBClientContext.java:588)
	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.doInvoke(EJBInvocationHandler.java:136)
	at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:121)
	at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:104)
	at com.sun.proxy.$Proxy14.invokeAll(Unknown Source)
	at org.jboss.as.quickstarts.ejb.multi.server.Client.main(Client.java:79)
	... 6 more

Also I see errors in server log file (see attached file)

Created attachment 770512 [details]
server errors after the client run

I test this fix with Wildfly Alpha 2 ( this is the only build that currently startup without errors) and it seems to work. I don't see any exceptions any more only few warnings but I don't believe they have anything to do with the original issue. I will ask the JBossTM guys to look at them.

We (EAP QA) are not able to reproduce the issue.
I've run the quickstart with transactions set to jts against several EAP Versions (6.0.1, 6.1.0, 6.1.1.ER3, 6.1.1.ER4) and I didn't hit the problem in any case.
I've consulted the my settings with Tom and neither after taking his settings of the configuration I was not able to hit the problem. Everything runs smoothly without the mentioned error.

We agreed with Tom that he will check this issue as soon as he will have time for it and in case that he will find it ok that he verified the issue.


I would like mention that:
 - there was a change in accesing rights to EJB bean. When EJB contains a security annotation then all methods are by default set to @DenyAll. To avoid this and be able to run the quickstart it's needed to set default-missing-method-permissions-deny-access to false in ejb3 subsystem
 - in case of out of memory errors it helped me to delete content of the domain/servers directory (rm -rf domain/servers/*)
 - problem on wildfly alpha3 (Caused by: java.lang.IllegalStateException: EJBCLIENT000025: No EJB receiver available for handling [appName:appmain, moduleName:ejb, distinctName:] combination) seems to be caused by the fact that remoting ports were changed. But I'm not sure how to change the quickstart to be working. I suppose that the default port was changed from 4777 to 8080 but I'm not fully sure.

The fix was tested on a WildFly build, as mentioned. QA was unable to reproduce with EAP, but verified the presence of the fix through JAR decompilation. We are nearing the end of test cycle and didn't receive enough feedback, so setting to VERIFIED as of EAP 6.1.1.ER4.

Tom Ross <toross> made a comment on jira WFLY-1362

I'm getting this exception when trying to run the test case. I don't believe this has anything to do with the original issue.

Caused by: javax.ejb.EJBException: java.lang.Exception: java.lang.NoClassDefFoundError: Could not initialize class com.arjuna.ats.internal.jts.OTSImpleManager
[Server:app-main] 	at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:236) [jboss-ejb-client-1.0.23.Final-redhat-1.jar:1.0.23.Final-redhat-1]
[Server:app-main] 	at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:181) [jboss-ejb-client-1.0.23.Final-redhat-1.jar:1.0.23.Final-redhat-1]
[Server:app-main] 	at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:144) [jboss-ejb-client-1.0.23.Final-redhat-1.jar:1.0.23.Final-redhat-1]
[Server:app-main] 	at com.sun.proxy.$Proxy33.invoke(Unknown Source)
[Server:app-main] 	at org.jboss.as.quickstarts.ejb.multi.server.app.MainAppBean.invokeAppOne(MainAppBean.java:129) [ejb.jar:]
[Server:app-main] 	... 54 more

Tom Ross <toross> made a comment on jira WFLY-1362

I'm getting this exception when trying to run the test case. I don't believe this has anything to do with the original issue.
{noformat}
Caused by: javax.ejb.EJBException: java.lang.Exception: java.lang.NoClassDefFoundError: Could not initialize class com.arjuna.ats.internal.jts.OTSImpleManager
[Server:app-main] 	at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:236) [jboss-ejb-client-1.0.23.Final-redhat-1.jar:1.0.23.Final-redhat-1]
[Server:app-main] 	at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:181) [jboss-ejb-client-1.0.23.Final-redhat-1.jar:1.0.23.Final-redhat-1]
[Server:app-main] 	at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:144) [jboss-ejb-client-1.0.23.Final-redhat-1.jar:1.0.23.Final-redhat-1]
[Server:app-main] 	at com.sun.proxy.$Proxy33.invoke(Unknown Source)
[Server:app-main] 	at org.jboss.as.quickstarts.ejb.multi.server.app.MainAppBean.invokeAppOne(MainAppBean.java:129) [ejb.jar:]
[Server:app-main] 	... 54 more
{noformat}