Description of problem:

compared to releases 2.2 & 2.3.0 (see BZ 910016), new issues became present in release 2.3.6, which result in the TCK transaction tests fail:

com/sun/ts/tests/jms/ee/ejbweb/xa/TransactionTests.java#Test02_from_ejb
com/sun/ts/tests/jms/ee/ejbweb/xa/TransactionTests.java#Test02_from_jsp
com/sun/ts/tests/jms/ee/ejbweb/xa/TransactionTests.java#Test02_from_servlet
com/sun/ts/tests/jms/ee/ejbweb/xa/TransactionTests.java#Test04_from_ejb
com/sun/ts/tests/jms/ee/ejbweb/xa/TransactionTests.java#Test04_from_jsp
com/sun/ts/tests/jms/ee/ejbweb/xa/TransactionTests.java#Test04_from_servlet

on the other hand, one issue reported earlier disapeared (for comparison see already mentioned, BZ 910016):

com/sun/ts/tests/jms/ee/ejbweb/xa/TransactionTests.java#Test08_from_servlet


Version-Release number of selected component (if applicable):

qpid-cpp-client-devel-0.18-18.el6.x86_64
qpid-jca-xarecovery-0.18-8.el6.noarch
qpid-cpp-client-0.18-18.el6.x86_64
qpid-java-common-0.18-8.el6_4.noarch
qpid-cpp-server-store-0.18-18.el6.x86_64
qpid-cpp-server-0.18-18.el6.x86_64
qpid-qmf-0.18-18.el6_4.x86_64
qpid-java-client-0.18-8.el6_4.noarch
qpid-cpp-server-ssl-0.18-18.el6.x86_64
qpid-cpp-client-devel-docs-0.18-18.el6.noarch
python-qpid-0.18-5.el6_4.noarch
python-qpid-qmf-0.18-18.el6_4.x86_64
qpid-java-example-0.18-8.el6_4.noarch
qpid-cpp-server-devel-0.18-18.el6.x86_64
qpid-jca-0.18-8.el6.noarch
qpid-cpp-server-xml-0.18-18.el6.x86_64
qpid-cpp-client-ssl-0.18-18.el6.x86_64
qpid-tools-0.18-10.el6_4.noarch