[ http://jira.jboss.com/jira/browse/JBAS-4467?page=all ] Dimitris Andreadis updated JBAS-4467: ------------------------------------- Fix Version/s: JBossAS-4.2.1.CR1 (was: JBossAS-4.2.2.CR1) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBAS-4467?page=all ] Dimitris Andreadis closed JBAS-4467. ------------------------------------ Resolution: Done Added to Compatibility Issues: "JBoss TS, the new default transaction manager will not let you enlist multiple 1-phase participants in the same transaction. This was *not* the default behavior with the legacy JBoss TM that would log a warning and continue. There are good reasons for this change, mainly to avoid heuristic outcomes in the case of system crashes, which is the primary reason of using a transaction manager anyway! If your come across this problem you should try to fix it by switching to XA resources or implementing some form of compensating transactions. However, if this is not option and you are fully aware of the consequences you can override this behavior by setting com.arjuna.ats.jta.allowMultipleLastResources to true in conf/jbossjta-properties.xml. For more details read the wiki on Multiple1PC, or consult the JBoss Transactions documentation." -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira