[ https://jira.jboss.org/jira/browse/ISPN-156?page=com.atlassian.jira.plugi... ] Manik Surtani updated ISPN-156: ------------------------------- Workaround Description: Not really a workaround; but this works fine with the DummyTransactionManager. Component/s: Transactions Fix Version/s: 4.0.0.BETA1 Affects Version/s: 4.0.0.ALPHA6 Complexity: High Priority: Blocker (was: Major) Workaround: [Workaround Exists] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/ISPN-156?page=com.atlassian.jira.plugi... ] Manik Surtani commented on ISPN-156: ------------------------------------ I've added a modified version of Lukasz's test to trunk. The test passes with the DummyTransactionManager but fails with JBossTS. The crux of the problem is that JBossTS performs commit() calls on the registered TransactionXAResource instance but no prepare(). This has to do with JBossTS optimising the transaction to a single-phase tx since there is only one resource registered. And this causes the TransactionXAResource to skip some vital steps in prepare(). The correct solution is to modify TransactionXAResource to call prepare() in commit(), if onePhase is true. The TM passes the onePhase parameter to commit() so this information is available. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira