Created attachment 524624 [details] TCK results TCK test sessionTtests is failing during TCK execution. There is no information in EAP server.log. The test result is 09-23-2011 07:07:20: ERROR: java.lang.Exception: Null message received! at com.sun.ts.tests.jms.ee.ejb.sessionTtests.Client.simpleSendReceiveT(Client.java:157) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.sun.ts.lib.harness.EETest.run(EETest.java:495) at com.sun.ts.lib.harness.EETest.getPropsReady(EETest.java:392) at com.sun.ts.lib.harness.EETest.run(EETest.java:252) at com.sun.ts.lib.harness.EETest.run(EETest.java:204) at com.sun.ts.tests.jms.ee.ejb.sessionTtests.Client.main(Client.java:54) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.ejb3.client.ClientContainer.invokeMain(ClientContainer.java:269) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.ejb3.client.ClientLauncher.launch(ClientLauncher.java:301) at org.jboss.ejb3.client.ClientLauncher.launch(ClientLauncher.java:174) at org.jboss.ejb3.client.ClientLauncher.launch(ClientLauncher.java:138) at org.jboss.client.AppClientMain.main(Ap The error is present if and only if the TCK is executed as the whole. I am not able to reproduce it when I execute only this single test. This also makes logging on broker impractical so I cannot provide those data.
Created attachment 524625 [details] TCK application
Being that this failure only occurs at the end of a full TCK run, I am loathe to keep this as an outstanding issue for this release being that a single test run completes successfully. As a result, I am moving this out for a later date.
This is an old bug and falls under our rubric of TCK edge failures. As a result, I am going to close it. More specifically, this one only fails at the very end of a TCK run and appeared to be transient.