[jboss-cvs] JBossAS SVN: r97196 - projects/docs/enterprise/4.3.7/Release_Notes/en-US.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Mon Nov 30 20:47:24 EST 2009
Author: laubai
Date: 2009-11-30 20:47:24 -0500 (Mon, 30 Nov 2009)
New Revision: 97196
Modified:
projects/docs/enterprise/4.3.7/Release_Notes/en-US/Release_Notes_CP07.xml
Log:
Added notes for JBPAPP-3106, 3140.
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-12-01 01:46:47 UTC (rev 97195)
+++ projects/docs/enterprise/4.3.7/Release_Notes/en-US/Release_Notes_CP07.xml 2009-12-01 01:47:24 UTC (rev 97196)
@@ -470,18 +470,7 @@
<title>JBoss Application Server</title>
<para>
<itemizedlist>
- <!--<listitem>
- <para>
- <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-3103">JBPAPP-3103</ulink>: #MODIFY
- </para>
- </listitem>-->
- <!-- #MODIFY - required? not broken in previous versions
<listitem>
- <para>
- <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-3099">JBPAPP-3099</ulink>: During startup, JBoss Application Server printed repetitive messages to the log, which could negatively affect performance. The line causing the excessive logging has been removed.
- </para>
- </listitem>-->
- <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>
@@ -505,7 +494,7 @@
<itemizedlist>
<listitem>
<para>
- <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-3109">JBPAPP-3109</ulink>: Some examples provided with Seam 2.0.2 failed on the client side because the <varname>exceptionHandler</varname> variable was not declared. The <methodname>execute()</methodname> method and method invocation generated within the event handler both require an <classname>exceptionHandler</classname> as an argument. <varname>exceptionHandler</varname> is now declared in the interface generator.
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-3112">JBPAPP-3112</ulink>:
</para>
</listitem>
<listitem>
@@ -629,27 +618,11 @@
<para>
<ulink url="https://jira.jboss.org/jira/browse/JBPAPP-3117">JBPAPP-3117</ulink>: If an incorrect <varname>mcast_addr</varname> value is set, users are pointed to an outdated URL for information about cross talking. If you experience problems with <varname>mcast_addr</varname> and cross talking, the updated URL for further information is <ulink url="https://www.jboss.org/community/docs/DOC-9469">https://www.jboss.org/community/docs/DOC-9469</ulink>.
</para>
- <!-- ORIGINAL TEXT FOR JBPAPP-3119
- </para>
- If the <varname>java.net.preferIPv4Stack</varname> or <varname>java.net.preferIPv6Stack</varname> property is not specified, JGroups prints a warning and exception similar to the following:
- </para>
- <screen>
-[JBoss] 05:57:35,544 WARN [UDP] could not bind to /234.1.78.86
- (IPv4 address); make sure your mcast_addr is of the same type
- as the preferred IP stack (IPv4 or IPv6) by checking the value
- of the system properties java.net.preferIPv4Stack and
- java.net.preferIPv6Addresses.
-[JBoss] Will ignore mcast_addr, but this may lead to cross
- talking (see http://www.jboss.com/wiki/Edit.jsp?page=CrossTalking
- for details).
-[JBoss] Exception was: java.net.BindException: Cannot assign
- requested address
- </screen>
+ </listitem>
+ <listitem>
<para>
- To work around this issue, be sure to specify your preferred IP stack (either <literal>IPv4</literal> or <literal>IPv6</literal>) at startup with one of the following switches:
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-3106">JBPAPP-3106</ulink>: The <varname>org.jboss.mx.loading.blacklistMode</varname> configuration parameter is case-sensitive.
</para>
- <programlisting>-Djava.net.preferIPv4Stack</programlisting>
- <programlisting>-Djava.net.preferIPv6Stack</programlisting>-->
</listitem>
<listitem>
<para>
@@ -939,6 +912,26 @@
</itemizedlist>
</para>
</formalpara>
+ <formalpara>
+ <title>JBoss Messaging Known Issues</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBPAPP-3140">JBPAPP-3140</ulink>: JBoss Messaging does not work correctly when used with MS SQL Server and MS JDBC driver 2.0 and the default adaptive buffering mode. Adaptive buffering only lets a query access a column once; subsequent attempts to access the column cause exceptions. The workaround for this issue is to use the <varname>responseBuffering</varname> parameter with the JDBC connection URL:
+ </para>
+ <programlisting><![CDATA[
+<url>jdbc:sqlserver://[host];database=[database];responseBuffering=full;</url>
+ ]]></programlisting>
+ <para>
+ The default value for <varname>responseBuffering</varname> is <literal>full</literal> for JDBC Driver version 1.2, and <literal>adaptive</literal> for version 2.0.
+ </para>
+ </listitem>
+
+
+ </itemizedlist>
+ </para>
+ </formalpara>
</section>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Revision_History.xml"/>
More information about the jboss-cvs-commits
mailing list