[jboss-cvs] JBossAS SVN: r89153 - projects/docs/enterprise/4.3.5/readme/en-US.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Tue May 19 23:13:48 EDT 2009
Author: irooskov at redhat.com
Date: 2009-05-19 23:13:48 -0400 (Tue, 19 May 2009)
New Revision: 89153
Modified:
projects/docs/enterprise/4.3.5/readme/en-US/Release_Notes_CP05.xml
Log:
updated release notes with new JIRA
Modified: projects/docs/enterprise/4.3.5/readme/en-US/Release_Notes_CP05.xml
===================================================================
--- projects/docs/enterprise/4.3.5/readme/en-US/Release_Notes_CP05.xml 2009-05-20 03:11:09 UTC (rev 89152)
+++ projects/docs/enterprise/4.3.5/readme/en-US/Release_Notes_CP05.xml 2009-05-20 03:13:48 UTC (rev 89153)
@@ -73,13 +73,13 @@
<para>
JAF 1.2_10
</para>
- </listitem>
+ </listitem> -->
<listitem>
<para>
- JBoss Cache 1.4.1.SP11
+ JBoss Cache 1.4.1_SP13
</para>
</listitem>
- <listitem>
+ <!-- <listitem>
<para>
JBoss JAXR 1.2.0.SP2
</para>
@@ -93,23 +93,23 @@
<para>
JBoss Remoting 2.2.2.SP11
</para>
- </listitem>
+ </listitem> -->
<listitem>
<para>
- JBoss Transactions 4.2.3.SP5.CP04
+ JBoss Transactions 4.2.3.SP5.CP05
</para>
</listitem>
- <listitem>
+ <!-- <listitem>
<para>
JBoss Web 2.0.0-6.CP09
</para>
- </listitem>
+ </listitem> -->
<listitem>
<para>
- JBoss Web Services 2.0.1.SP2_CP05
+ JBoss Web Services 2.0.1.SP2_CP06
</para>
</listitem>
- <listitem>
+ <!-- <listitem>
<para>
JGroups 2.4.5
</para>
@@ -381,14 +381,21 @@
<itemizedlist>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1995">JBPAPP-1995</ulink>: The <methodname>RegionManager.createRegion</methodname> method would allow duplicate region names and when this occurs all future cache operations would happen only on the second instance of the region, while the <methodname>EvictionTimerTask</methodname> will only watch the first instance, causing the eviction queue of the second instance to fill. To correct this bug, the <methodname>RegionManager.checkConflict</methodname> method now counts a duplicate as a conflict and causes the <methodname>RegionManager.createRegion</methodname> method to generate an exception.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1993">JBPAPP-1993</ulink>: The JBoss Cache component of the Enterprise Application Platform has been upgraded to version 1.4.1_SP13. A list of the included fixes is as follows:
</para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1995">JBPAPP-1995</ulink>: The <methodname>RegionManager.createRegion</methodname> method would allow duplicate region names and when this occurs all future cache operations would happen only on the second instance of the region, while the <methodname>EvictionTimerTask</methodname> will only watch the first instance, causing the eviction queue of the second instance to fill. To correct this bug, the <methodname>RegionManager.checkConflict</methodname> method now counts a duplicate as a conflict and causes the <methodname>RegionManager.createRegion</methodname> method to generate an exception.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1994">JBPAPP-1994</ulink>: The <methodname>findNode</methodname> method of TreeCache generated a <exceptionname>NullPointerException</exceptionname> when the <methodname>findInternal</methodname> method returned a null value. The <methodname>findNode</methodname> method can now handle a null value returned from the <methodname>findInternal</methodname> method by checking within the <filename>TreeCache.java</filename> file if the <varname>toReturn</varname> value is null as well as the <varname>version</varname>
+ </para>
+ </listitem>
+ </itemizedlist>
</listitem>
- <listitem>
- <para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1994">JBPAPP-1994</ulink>: The <methodname>findNode</methodname> method of TreeCache generated a <exceptionname>NullPointerException</exceptionname> when the <methodname>findInternal</methodname> method returned a null value. The <methodname>findNode</methodname> method can now handle a null value returned from the <methodname>findInternal</methodname> method by checking within the <filename>TreeCache.java</filename> file if the <varname>toReturn</varname> value is null as well as the <varname>version</varname>
- </para>
- </listitem>
</itemizedlist>
</para>
</formalpara>
@@ -422,6 +429,23 @@
<itemizedlist>
<listitem>
<para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1993">JBPAPP-1993</ulink>: The JBoss Web Services component of the Enterprise Application Platform has been upgraded to version 2.0.1.SP2_CP06. A list of the included fixes is as follows:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1784">JBPAPP-1784</ulink>: When starting the Enterprise Application Platform with the <code>-Dcom.sun.management.jmxremote</code> option, a <exceptionname>NullPointerException</exceptionname> would occur. The <filename>SubscriptionManager.java</filename> file was updated to allow for a break in the <classname>MBeanServer</classname> if the <classname>MBeanServer</classname> server class name starts with <emphasis>org.jboss</emphasis>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1732">JBPAPP-1732</ulink>: The MTOM/XOP message always set the <property>start-info</property> property to <code>text/xml</code> when it should have been set to <code>application/soap+xml</code>. This bug was introduced through an upgrade from SOAP 1.1 to SOAP 1.2. The SOAP HTTP binding in the <property>Content-type</property> header has now been updated to the correct value.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ <listitem>
+ <para>
<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-829">JBPAPP-829</ulink>: Authentication and authorization needed to be added for POJO endpoints where credentials are supplied using Web Services Security. In order to rectify this issue the following list of files were updated or added as specified:
</para>
<itemizedlist>
@@ -589,8 +613,13 @@
<itemizedlist>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1684">JBPAPP-1684</ulink>: A memory leak would be caused in the <classname>BaseTransaction</classname> class because entries in the hash table were never removed, even if a thread was no longer in use. This meant that client transactions could have leaked approximately 600 bytes. To correct this bug, the <filename>BaseTransaction.java</filename> file has been updated to replace the hash table with a <varname>ThreadLocal</varname> implementation which takes an integer as input. In order to allow for the timeout values to work correctly, they now only call the required methods of <methodname>_timeouts.set</methodname> and <methodname>_timeouts.get</methodname>. With these improvements made, the memory leak no longer occurs.
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1693">JBPAPP-1693</ulink>: The JBoss Transaction Service component of the Enterprise Application Platform has been upgraded to version 4.2.3.SP5.CP05. A list of the included fixes is as follows:
</para>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1684">JBPAPP-1684</ulink>: A memory leak would be caused in the <classname>BaseTransaction</classname> class because entries in the hash table were never removed, even if a thread was no longer in use. This meant that client transactions could have leaked approximately 600 bytes. To correct this bug, the <filename>BaseTransaction.java</filename> file has been updated to replace the hash table with a <varname>ThreadLocal</varname> implementation which takes an integer as input. In order to allow for the timeout values to work correctly, they now only call the required methods of <methodname>_timeouts.set</methodname> and <methodname>_timeouts.get</methodname>. With these improvements made, the memory leak no longer occurs.
+ </para>
+ </listitem>
</listitem>
</itemizedlist>
</para>
More information about the jboss-cvs-commits
mailing list