[jboss-cvs] JBossAS SVN: r95161 - projects/docs/enterprise/5.0/Release_Notes_GA/en-US.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Tue Oct 20 04:33:47 EDT 2009
Author: laubai
Date: 2009-10-20 04:33:47 -0400 (Tue, 20 Oct 2009)
New Revision: 95161
Modified:
projects/docs/enterprise/5.0/Release_Notes_GA/en-US/Release_Notes.xml
Log:
Documented JBPAPPs 2948, 2924, 2900, 2892, 2866, 2858, 2791, 2306, 2033, 1998, 1230 for GA.
Modified: projects/docs/enterprise/5.0/Release_Notes_GA/en-US/Release_Notes.xml
===================================================================
--- projects/docs/enterprise/5.0/Release_Notes_GA/en-US/Release_Notes.xml 2009-10-20 08:06:33 UTC (rev 95160)
+++ projects/docs/enterprise/5.0/Release_Notes_GA/en-US/Release_Notes.xml 2009-10-20 08:33:47 UTC (rev 95161)
@@ -227,7 +227,7 @@
</row>
<row>
<entry>JBoss Messaging</entry>
- <entry>1.4.5.GA</entry>
+ <entry>1.4.6.GA</entry>
<entry>1.4.0.SP3-CP08.patch01</entry>
</row>
<row>
@@ -578,7 +578,7 @@
JSR-181 related functionality is not supported in this version of the JBoss Enterprise Application Platform. This functionality will be supported in version 4.3.
</para>
</section>-->
-<!--
+
<section id="Issues-fixed-in-this-release">
<title>
Issues fixed in this release
@@ -587,7 +587,25 @@
<para>
Following is a list of issues fixed in this release:
</para>
- <formalpara>
+ <formalpara>
+ <title>JBoss Application Server</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2866">JBPAPP-2866</ulink>: The JGroups protocol stack included an incorrect diagnostic address, <literal>224.0.0.75</literal>. The address has been corrected to <literal>224.0.75.75</literal>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2306">JBPAPP-2306</ulink>: The HP-UX init script in the First Customer Ship, <filename>jboss_init_hpux.sh</filename>, did not let users define a bind address with the <code>-b</code> option. Support for this option has since been added to the script.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </formalpara>
+ <!--#MODIFY: ADD CHANGES BTW 1.4.3 and 1.4.6.
+ <formalpara>
<title>JBoss Messaging</title>
<para>
<itemizedlist>
@@ -598,8 +616,8 @@
</listitem>
</itemizedlist>
</para>
- </formalpara>
- <formalpara>
+ </formalpara>-->
+ <!--<formalpara>
<title>JBoss Cache</title>
<para>
<itemizedlist>
@@ -658,19 +676,20 @@
</listitem>
</itemizedlist>
</para>
- </formalpara>
+ </formalpara>-->
<formalpara>
<title>JBoss Hibernate</title>
<para>
<itemizedlist>
<listitem>
<para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2900">JBPAPP-2900</ulink>: MySQL uses the <literal>TEMPORARY</literal> keyword to bypass implicit transaction commits. Previously, Hibernate used <code><CREATE TEMPORARY TABLE></code> with <code><DROP TABLE></code>. Omitting the <literal>TEMPORARY</literal> keyword caused an implicit commit, and immediate failure within an XA Transaction. <code><DROP TEMPORARY TABLE></code> is now supported and this issue no longer presents.
</para>
</listitem>
</itemizedlist>
</para>
</formalpara>
- <formalpara>
+ <!--<formalpara>
<title>JBoss Transaction Service (JBossTS)</title>
<para>
<itemizedlist>
@@ -732,8 +751,8 @@
</listitem>
</itemizedlist>
</para>
- </formalpara>
- </section> -->
+ </formalpara>-->
+ </section>
<section id="Known_Issues_with_this_release">
<title>
Known Issues with this release
@@ -745,6 +764,11 @@
<title>General Known Issues</title>
<para>
<itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2948">JBPAPP-2948</ulink>: The <filename>deploy/jmx-remoting.sar</filename> that instantiates a JSR-160 adapter for remote access to the JBoss MBeanServer for use with tools such as the JConsole does not currently support secure access. This presents a security risk in production environments where a specific address is accessed via this JSR-160 adapter. We strongly recommend disabling this adapter by undeploying or removing the <filename>deploy/jmx-remoting.sar</filename> directory.
+ </para>
+ </listitem>
<listitem>
<para>
<ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2571">JBPAPP-2571</ulink>: Running the Microsoft SQL server with Microsoft JDBC drivers 2.0 causes unstable builds in JBoss Messaging. This issue is created by the <literal>Adaptive Buffering</literal> being the default behavior for the driver as this only allows for large values ot be read once by using the <methodname>get<Type>Stream</methodname> method. The current workaround for this issue is to change the <parameter>responseBuffering</parameter> parameter of the JDBC connection URL from being <literal>adaptive</literal>, to being <literal>full</literal> (as it was for version 1.2 of the JDBC driver).
@@ -798,12 +822,23 @@
<ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2894">JBPAPP-2894</ulink>: Setting the <literal>hibernate.bytecode.provider</literal> system property in <filename>jpa-deployers-jboss-beans.xml</filename> is unreliable. The workaround for this issue is to add <code>-Dhibernate.bytecode.provider=cglib</code> to <literal>$JAVA_OPTS</literal> in <filename>jboss-as/bin/run.conf</filename>.
</para>
</listitem>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2892">JBPAPP-2892</ulink>: When Enterprise JavaBean 3.0 entities are used with optimistic caching, <classname>org.jboss.ejb3.entity.OptimisticJBCCache.DataVersionAdapter.newerThan</classname> incorrectly returns <literal>true</literal> for <literal>A.newerThan ( A )</literal>. This causes a <exceptionname>DataVersioningException</exceptionname> when JBoss Cache attempts to remove the entry. The workaround for this issue is to use Multiversion Concurrency Control (<literal>mvcc-entity</literal>) instead of optimistic caching. This is recommended even if the exception has not been observed.
+ </para>
+ </listitem>
<listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2818">JBPAPP-2818</ulink>: The current <filename>main/src/bin/run.sh</filename> does not allow users to override <filename>$JBOSS_HOME/bin/run.conf</filename> with a profile-specific <filename>$JBOSS_HOME/server/$PROFILE/run.conf</filename>.
+ </para>
+ </listitem>
+ <listitem>
<para>
- <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2384">JBPAPP-2384</ulink>: The Seam Chatroom example throws an <exceptionname>EJBTransactionRolledbackException</exceptionname> when a user attempts to log in. This exception does not influence the application's functionality.
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2713">JBPAPP-2713</ulink>: <classname>org.jboss.test.xml.DDValidatorUnitTestCase</classname> constantly fails and crashes the Java Virtual Machine. The workaround for this issue is to disable the JIT compiler by setting <code>JAVA_COMPILER=NONE</code> or using the command line switch <code>-Djava.compiler=NONE</code>.
</para>
- </listitem>
+ </listitem>
+
<!-- <listitem>
<para>
@@ -922,6 +957,11 @@
<ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2792">JBPAPP-2792</ulink>: Sybase fails to insert a new entity if it overflows its column. However, it does not throw an exception, so Hibernate cannot tell that the insert failed. To work around this issue, the application must validate entity properties to ensure that they do not overflow the underlying column.
</para>
</listitem>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2791">JBPAPP-2791</ulink>: <literal>SchemaUpdate</literal>s fail in Sybase ASE 15 tables when a new column is added without a default value. To work around this issue, ensure that a default value is included when adding new columns with <literal>SchemaUpdate</literal>.
+ </para>
+ </listitem>
<listitem>
<para>
<ulink url="https://jira.jboss.org/jira/browse/JBPAPP-1613">JBPAPP-1613</ulink>: Null values for columns mapped as <literal>Boolean</literal> in Sybase are persisted as <literal>0</literal> instead of <literal>null</literal>. The workaround for this issue is to map <code>type="org.hibernate.test.where.NumericTrueFalseType"</code> instead of <code>type="boolean"</code>.
@@ -948,7 +988,24 @@
The current recommendation is to not use join fetches that involve union subclasses.
</para>
</listitem>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2858">JBPAPP-2858</ulink>: <literal>getSingleResult()</literal> fails for some databases and queries when automatic pagination is attempted. The workaround for this issue is to use <literal>getResultList()</literal> instead of <literal>getSingleResult()</literal>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-1998">JBPAPP-1998</ulink>: The <classname>testUpdatedAndRemove</classname> and <classname>RemoveTest</classname> tests fail because an incorrect exception is thrown upon an optimistic locking failure when a deleted entity uses <varname>hibernate.jdbc.batch_versioned_data</varname> set to <literal>false</literal>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-1230">JBPAPP-1230</ulink>: Subqueries that use <literal>DetachedCriteria</literal> are generated incorrectly, which causes a <exceptionname>SybSQLException</exception>. The workaround for this issue is not to use <literal>DetachedCriteria</literal> in a subquery. Instead, we recommend using an HQL query.
+ </para>
+ </listitem>
+
+
<!-- <listitem>
<para>
<ulink url="">JBPAPP- </ulink>:
@@ -958,6 +1015,23 @@
</para>
</formalpara>
<formalpara>
+ <title>Seam Known Issues</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2384">JBPAPP-2384</ulink>: The Seam Chatroom example throws an <exceptionname>EJBTransactionRolledbackException</exceptionname> when a user attempts to log in. This exception does not influence the application's functionality.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2733">JBPAPP-2733</ulink>: When the Seam examples are tested with the TestNG plugin in JBDS, a <exceptionname>java.lang.AssertionError</exceptionname> is thrown. There is currently no workaround for this issue.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </formalpara>
+ <formalpara>
<title>JBoss Messaging Known Issues</title>
<para>
<itemizedlist>
@@ -974,6 +1048,11 @@
<ulink url="https://jira.jboss.org/jira/browse/JBMESSAGING-1746">JBPAPP-1746</ulink>: When JGroups is upgraded to version 2.6.13, the JBoss Messaging <literal>LargeClusterTest</literal> fails. The test attempts to start seven nodes on one machine before testing, but some nodes fail to start. The test passes if the number of nodes is reduced.
</para>
</listitem>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-2033">JBPAPP-2033</ulink>: <varname>EnableMessageCounters</varname> on the <classname>jboss.messaging.ServerPeer</classname> JMX interface, cannot be set to <literal>true</literal>. A workaround to enable message counters is to invoke the <classname>enableMessageCounters()</classname> operation on the same JMX interface.
+ </para>
+ </listitem>
</itemizedlist>
</para>
</section>
More information about the jboss-cvs-commits
mailing list