[jboss-cvs] JBossAS SVN: r96626 - projects/docs/enterprise/4.3.7/Release_Notes/en-US.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Fri Nov 20 02:13:48 EST 2009
Author: laubai
Date: 2009-11-20 02:13:47 -0500 (Fri, 20 Nov 2009)
New Revision: 96626
Modified:
projects/docs/enterprise/4.3.7/Release_Notes/en-US/Release_Notes_CP07.xml
Log:
Adding release notes for JBPAPP-2872, 2854, 2782, 2764, 2578, 2312.
Modified: projects/docs/enterprise/4.3.7/Release_Notes/en-US/Release_Notes_CP07.xml
===================================================================
--- projects/docs/enterprise/4.3.7/Release_Notes/en-US/Release_Notes_CP07.xml 2009-11-20 07:09:35 UTC (rev 96625)
+++ projects/docs/enterprise/4.3.7/Release_Notes/en-US/Release_Notes_CP07.xml 2009-11-20 07:13:47 UTC (rev 96626)
@@ -373,6 +373,55 @@
<para>
Following is a list of issues fixed in this release:
</para>
+ <formalpara>
+ <title>Security</title>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2872">JBPAPP-2872</ulink>: Twiddle logged all command line arguments, including the JMX password, to <filename>twiddle.log</filename>, which had public read permissions, and was created in the current working directory. The password is now masked in the log, removing the risk to security.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2312">JBPAPP-2312</ulink>: A new <classname>PrincipalSessionAttributeFilter</classname> has been created to include the principal session as an attribute of the HTTP Session. This attribute is checked upon session expiry and the authenticated cache will be flushed if found. In order to use this filter, uncomment the filter in Tomcat's <filename>web.xml</filename>.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </formalpara>
+ <formalpara>
+ <title>JBoss Application Server</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2905">JBPAPP-2905</ulink>: The <varname>ScanPeriod</varname> in the <literal>production</literal> configuration is set to sixty seconds. If the deployment scanner thread was sleeping when shutdown was initiated, shutdown waited for the length of the deployment scanner's sleep time. The deployment scanner thread is now stopped when shutdown is initiated, and the wait no longer occurs.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2764">JBPAPP-2764</ulink>: <classname>LoadMgr3</classname> logged a failure to load a class as an error, but in certain situations this should be regarded as correct. The <literal>ERROR</literal> message has been downgraded to a <literal>WARNING</literal>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2578">JBPAPP-2578</ulink>: Configuration information for the JBoss Messaging service in <filename>sample-bindings.xml</filename> has been updated to make use of new settings.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>JBoss Seam</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2967">JBPAPP-2967</ulink>: A shared value binding returned a <literal>null</literal> value when under load, which caused a <exceptionname>javax.el.PropertyNotFoundException</exceptionname>. The value binding is no longer shared and the issue no longer presents.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </formalpara>
<formalpara>
<title>JBoss Hibernate</title>
<para>
@@ -410,7 +459,7 @@
</listitem>
<listitem>
<para>
- <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-1998">JBPAPP-1998</ulink>: <exceptionname>EntityNotFoundException</exceptionname> is incorrectly thrown upon an optimistic locking failure when one <literal>EntityManager</literal> tries to delete an entity that has been updated by a different <literal>EntityManager</literal> and <varname>hibernate.jdbc.batch_versioned_data</varname> is set to <literal>false</literal> (the default value). <exceptionname>OptimisticLockException</exception>, the correct exception for this situation, is now thrown instead.
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-1998">JBPAPP-1998</ulink>: <exceptionname>EntityNotFoundException</exceptionname> is incorrectly thrown upon an optimistic locking failure when one <literal>EntityManager</literal> tries to delete an entity that has been updated by a different <literal>EntityManager</literal> and <varname>hibernate.jdbc.batch_versioned_data</varname> is set to <literal>false</literal> (the default value). <exceptionname>OptimisticLockException</exceptionname>, the correct exception for this situation, is now thrown instead.
</para>
</listitem>
<listitem>
@@ -424,6 +473,42 @@
</itemizedlist>
</para>
</formalpara>
+ <formalpara>
+ <title>Clustering</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2854">JBPAPP-2854</ulink>: When multiple nodes were started concurrently, an address mismatch would occur between cluster members and message senders. This caused inconsistent internal state in <literal>NAKACK</literal>, which would log errors similar to the following:
+ </para>
+ <programlisting>
+WARN [org.jgroups.protocols.pbcast.NAKACK]
+ (IncomingPacketHandler (channel=Tomcat-DefaultPartition):)
+ node2:1234] discarded message from non-member node3:1234,
+ my view is [node1:1234|2] [node1:1234, node2:1234, node3:1234]
+
+ERROR [org.jgroups.protocols.pbcast.NAKACK] (Timer-3:)
+ sender node3:1234 not found in received_msgs
+ </programlisting>
+ <para>
+ This mismatch has been corrected and the errors no longer present.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>EJB3</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2782">JBPAPP-2782</ulink>: When EJB3 entities were used with optimistic caching, the <methodname>newerThan</methodname> method would incorrectly return <literal>true</literal> for <code>A.newerThan ( A )</code>. This caused a <exceptionname>DataVersioningException</exceptionname> when attempting to remove the entry from the cache. The EJB3 entity cache service is now configured to use pessimistic caching to avoid this issue.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </formalpara>
</section>
<section id="Known_Issues_with_this_release">
<title>
@@ -584,7 +669,7 @@
<listitem>
<para>
The JPA specification defines the constant with a value that has a typo in the classname:
- <para>
+ </para>
<programlisting>javax.persistence.Persistence.PERSISTENCE_PROVIDER = "javax.persistence.spi.PeristenceProvider"</programlisting>
<para>
Because the JAR inluded in the JBoss Enterprise Application Platform does not include this typo, it is not compliant with the JPA specification. See <ulink url="http://opensource.atlassian.com/projects/hibernate/browse/EJB-321">http://opensource.atlassian.com/projects/hibernate/browse/EJB-321</ulink> for details.
@@ -604,7 +689,7 @@
</listitem>
<listitem>
<para>
- <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-1555">JBPAPP-1555</ulink>: Sybase uses <literal>image</literal> and <literal>text</literal> instead of <literal>Blob</literal> and </literal>Clob</literal>, so there is no support for <literal>Blob</literal> and <literal>Clob</literal> on Sybase. This feature is expected in JBoss Enterprise Application Platform 5.1.0.GA. Currently, user-defined types can be created to process Sybase <literal>text</literal> and <literal>image</literal> properties.
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-1555">JBPAPP-1555</ulink>: Sybase uses <literal>image</literal> and <literal>text</literal> instead of <literal>Blob</literal> and <literal>Clob</literal>, so there is no support for <literal>Blob</literal> and <literal>Clob</literal> on Sybase. This feature is expected in JBoss Enterprise Application Platform 5.1.0.GA. Currently, user-defined types can be created to process Sybase <literal>text</literal> and <literal>image</literal> properties.
</para>
</listitem>
<listitem>
@@ -627,7 +712,7 @@
Explicitly call <methodname>session.save()</methodname> on child objects to enforce their SQL insertion orders.
</para>
</listitem>
- <itemizedlist>
+ </itemizedlist>
</listitem>
<listitem>
<para>
@@ -676,7 +761,7 @@
</listitem>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1082">JBPAPP-1082</ulink>: When a <varname>char</varname> property is used and it is not initialized, then Hibernate initializes it to <literal>0</literal> and persists a string containing the character <literal>\u0000</literal>. PostgreSQL throws an exception because it does not allow character <literal>\u0000</litearl> embedded in a string. An email thread describing this problem is available from:
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1082">JBPAPP-1082</ulink>: When a <varname>char</varname> property is used and it is not initialized, then Hibernate initializes it to <literal>0</literal> and persists a string containing the character <literal>\u0000</literal>. PostgreSQL throws an exception because it does not allow character <literal>\u0000</literal> embedded in a string. An email thread describing this problem is available from:
</para>
<itemizedlist>
<listitem>
More information about the jboss-cvs-commits
mailing list