org.jboss.test.cts.test.StatefulSessionUnitTestCase.testBadUserTx incorrectly uses JMX lookup of tx statistics to verify the outcome. There are two issues with this approach

1) The exposure of tx statistics is not part of the tx integration API, it's an implementation detail of the tx manager, so it should not be relied upon. Perhaps a Synchronization instead?
2) Even if it is decided to continue with this close coupling of the test suite to a component implementation, the test does not enable statistics gathering. Since this is off by default for performance reasons, the tx counter will always be 0. This may cause the test to pass in cases where it should not.