[jboss-cvs] JBossAS SVN: r63573 - branches/Branch_4_2/build/docs.

[jboss-cvs-commits at lists.jboss.org]

Author: dimitris at jboss.org
Date: 2007-06-19 13:25:55 -0400 (Tue, 19 Jun 2007)
New Revision: 63573

Modified:
   branches/Branch_4_2/build/docs/readme.html
Log:
JBAS-4467, Document in the release notes a configuration for multiple 1PC with JBossTS

Modified: branches/Branch_4_2/build/docs/readme.html
===================================================================
--- branches/Branch_4_2/build/docs/readme.html	2007-06-19 17:12:30 UTC (rev 63572)
+++ branches/Branch_4_2/build/docs/readme.html	2007-06-19 17:25:55 UTC (rev 63573)
@@ -189,6 +189,20 @@
 	wiki page on
 	<a href="http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossVersionCompatibilityMatrix">
 	JBoss Version Compatibility</a>.</li>
+	<li>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
+	<a href="http://wiki.jboss.org/wiki/Wiki.jsp?page=Multiple1PC">Multiple1PC</a>, 
+	or consult the <a href="http://labs.jboss.com/jbosstm/docs/index.html">JBoss 
+	Transactions documentation</a>.</li>
 </ul>
 <h2><a name="Configuration">Configuration Issues</a></h2>This lists the changes that could affect configuration.<ul>
 	<li>JBossAS now binds its services to localhost (127.0.0.1) *by default*,