[jboss-cvs] JBossAS SVN: r83638 - in projects/docs/enterprise: 4.3.4/readme/en-US and 1 other directory.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Thu Jan 29 23:34:30 EST 2009
Author: irooskov at redhat.com
Date: 2009-01-29 23:34:30 -0500 (Thu, 29 Jan 2009)
New Revision: 83638
Modified:
projects/docs/enterprise/4.2.6/readme/en-US/Release_Notes_CP06.xml
projects/docs/enterprise/4.3.4/readme/en-US/Release_Notes_CP04.xml
Log:
added JBPAPP-1510 transaction changes to release notes
Modified: projects/docs/enterprise/4.2.6/readme/en-US/Release_Notes_CP06.xml
===================================================================
--- projects/docs/enterprise/4.2.6/readme/en-US/Release_Notes_CP06.xml 2009-01-30 02:06:00 UTC (rev 83637)
+++ projects/docs/enterprise/4.2.6/readme/en-US/Release_Notes_CP06.xml 2009-01-30 04:34:30 UTC (rev 83638)
@@ -645,16 +645,65 @@
</itemizedlist>
</para>
</formalpara>
- <!-- <formalpara>
+ <formalpara>
<title>JBoss Transaction Service (JBossTS)</title>
<para>
<itemizedlist>
<listitem>
-
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1510">JBPAPP-1510</ulink>: The JBoss Transaction Service component of the EAP has been upgraded to version 4.2.3.SP5.CP04. A list of the included fixes is as follows:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ The <classname>AppServerJDBCXARecovery</classname> class was using the Java 1.5 syntax when it should compile with Java 1.4. This error has been rectified with this release by modifying the <filename>AppServerJDBCXARecovery.java</filename> file to use Java 1.4.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ When the Application Server started, the transaction manager may have deployed before the datasources, starting a recovery pass and causing exceptions. This issue has been rectified by modifying the <classname>AppServerJDBCXARecovery</classname> class and adding the <methodname>createConnection() throws SQLException</methodname> method which makes sure a connection exists before deploying the transaction manager.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ There were occurances when the <classname>AppServerJDBCXARecovery</classname> class would contain information to an invalid connection because of database failure. This bug was fixed with the same correction as the above issue, which is, by modifying the <classname>AppServerJDBCXARecovery</classname> class and adding the <methodname>createConnection() throws SQLException</methodname> method which makes sure a connection exists.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The <methodname>beforeCompletion</methodname> method would be run even when the <literal>tx</literal> state was set to <varname>ABORT_ONLY</varname>, when this method should only be executed before commit attempts and not rollbacks. In order to correct this and make sure the <methodname>beforeCompletion</methodname> method does not get executed for rollback events the <filename>SubordinateAtomicAction.java</filename> file has been modified.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <methodname>TransactionImple.doOnePhaseCommit</methodname> would generate a <exceptionname>HeuristicRollbackException</exceptionname> when the commit was aborted. This meant that <methodname>XATerminatorImple.commit</methodname> was unable to distingush between a successful rollback and one in error. Fixed in this CP release, the <filename>TransactionImple.java</filename> file has been modified so that the <methodname>TransactionImple.doOnePhaseCommit</methodname> method now generates a <exceptionname>RollbackException</exceptionname> instead of a heuristic when a successful rollback is performed.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ When the <literal>tx</literal> had been set to <varname>rollbackOnly</varname> and the <methodname>XATerminatorImple.prepare</methodname> method was called, a <exceptionname>XA_RBROLLBACK</exceptionname> exception would be generated and yet the rollback would not be undertaken and the <literal>tx</literal> reference would be removed meaning no cleanup via the <methodname>commit</methodname> or <methodname>rollback</methodname> methods were possible. The <filename>XATerminatorImple.java</filename> file has been updated to correct this by improving the cleanup and exception reporting for rollbacks in <methodname>XATerminatorImple.prepare</methodname>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The <methodname>SubordinateAtomicAction.doPrepare</methodname> method called <methodname>beforeCompletion</methodname> but did not call <methodname>afterCompletion</methodname> when the return status was <literal>Read Only</literal>. <filename>SubordinateAtomicAction.java</filename> now has corrected synchronization handling for transaction termination.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The JCA coordinator did not call synchronizations during the phase commit cycle (1PC). Synchronization has been added to the JCA coordinator through the modification of the <filename>SubordinateAtomicAction.java</filename> file.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Coordinator methods would not perform a cleanup correctly. In order to rectify this cleanup routines have been added to the <methodname>phase2Commit</methodname> and <methodname>phase2Abort</methodname> methods.
+ </para>
+ </listitem>
+ </itemizedlist>
</listitem>
</itemizedlist>
</para>
- </formalpara> -->
+ </formalpara>
<formalpara>
<title>Security Issues</title>
<para>
Modified: projects/docs/enterprise/4.3.4/readme/en-US/Release_Notes_CP04.xml
===================================================================
--- projects/docs/enterprise/4.3.4/readme/en-US/Release_Notes_CP04.xml 2009-01-30 02:06:00 UTC (rev 83637)
+++ projects/docs/enterprise/4.3.4/readme/en-US/Release_Notes_CP04.xml 2009-01-30 04:34:30 UTC (rev 83638)
@@ -742,16 +742,65 @@
</itemizedlist>
</para>
</formalpara>
- <!-- <formalpara>
+ <formalpara>
<title>JBoss Transaction Service (JBossTS)</title>
<para>
<itemizedlist>
<listitem>
-
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1510">JBPAPP-1510</ulink>: The JBoss Transaction Service component of the EAP has been upgraded to version 4.2.3.SP5.CP04. A list of the included fixes is as follows:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ The <classname>AppServerJDBCXARecovery</classname> class was using the Java 1.5 syntax when it should compile with Java 1.4. This error has been rectified with this release by modifying the <filename>AppServerJDBCXARecovery.java</filename> file to use Java 1.4.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ When the Application Server started, the transaction manager may have deployed before the datasources, starting a recovery pass and causing exceptions. This issue has been rectified by modifying the <classname>AppServerJDBCXARecovery</classname> class and adding the <methodname>createConnection() throws SQLException</methodname> method which makes sure a connection exists before deploying the transaction manager.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ There were occurances when the <classname>AppServerJDBCXARecovery</classname> class would contain information to an invalid connection because of database failure. This bug was fixed with the same correction as the above issue, which is, by modifying the <classname>AppServerJDBCXARecovery</classname> class and adding the <methodname>createConnection() throws SQLException</methodname> method which makes sure a connection exists.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The <methodname>beforeCompletion</methodname> method would be run even when the <literal>tx</literal> state was set to <varname>ABORT_ONLY</varname>, when this method should only be executed before commit attempts and not rollbacks. In order to correct this and make sure the <methodname>beforeCompletion</methodname> method does not get executed for rollback events the <filename>SubordinateAtomicAction.java</filename> file has been modified.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <methodname>TransactionImple.doOnePhaseCommit</methodname> would generate a <exceptionname>HeuristicRollbackException</exceptionname> when the commit was aborted. This meant that <methodname>XATerminatorImple.commit</methodname> was unable to distingush between a successful rollback and one in error. Fixed in this CP release, the <filename>TransactionImple.java</filename> file has been modified so that the <methodname>TransactionImple.doOnePhaseCommit</methodname> method now generates a <exceptionname>RollbackException</exceptionname> instead of a heuristic when a successful rollback is performed.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ When the <literal>tx</literal> had been set to <varname>rollbackOnly</varname> and the <methodname>XATerminatorImple.prepare</methodname> method was called, a <exceptionname>XA_RBROLLBACK</exceptionname> exception would be generated and yet the rollback would not be undertaken and the <literal>tx</literal> reference would be removed meaning no cleanup via the <methodname>commit</methodname> or <methodname>rollback</methodname> methods were possible. The <filename>XATerminatorImple.java</filename> file has been updated to correct this by improving the cleanup and exception reporting for rollbacks in <methodname>XATerminatorImple.prepare</methodname>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The <methodname>SubordinateAtomicAction.doPrepare</methodname> method called <methodname>beforeCompletion</methodname> but did not call <methodname>afterCompletion</methodname> when the return status was <literal>Read Only</literal>. <filename>SubordinateAtomicAction.java</filename> now has corrected synchronization handling for transaction termination.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The JCA coordinator did not call synchronizations during the phase commit cycle (1PC). Synchronization has been added to the JCA coordinator through the modification of the <filename>SubordinateAtomicAction.java</filename> file.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Coordinator methods would not perform a cleanup correctly. In order to rectify this cleanup routines have been added to the <methodname>phase2Commit</methodname> and <methodname>phase2Abort</methodname> methods.
+ </para>
+ </listitem>
+ </itemizedlist>
</listitem>
</itemizedlist>
</para>
- </formalpara> -->
+ </formalpara>
<formalpara>
<title>Security Issues</title>
<para>
More information about the jboss-cvs-commits
mailing list