[jboss-cvs] JBossAS SVN: r91265 - projects/docs/enterprise/4.3.5/readme/en-US.

[jboss-cvs-commits at lists.jboss.org]

Author: irooskov at redhat.com
Date: 2009-07-14 18:19:57 -0400 (Tue, 14 Jul 2009)
New Revision: 91265

Modified:
   projects/docs/enterprise/4.3.5/readme/en-US/Release_Notes_CP05.xml
Log:
removed EAP and replaced with Enterprise Application Platform and also copied JBM warning into Section 2.1 as well as in the Important Notes


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-07-14 22:12:52 UTC (rev 91264)
+++ projects/docs/enterprise/4.3.5/readme/en-US/Release_Notes_CP05.xml	2009-07-14 22:19:57 UTC (rev 91265)
@@ -35,6 +35,14 @@
 			<para>
 				In JBoss Enterprise Application Platform 4.3, JBoss MQ 1.3 has been replaced with JBoss Messaging 1.4. JBoss Messaging provides a high performance messaging infrastructure for JBoss Enterprise Application Platform.
 			</para>
+			<para>
+				A known issue exists within the JBoss Messaging component that allows for duplicate message IDs to be generated and may cause production software issues. Enterprise Application Platform 4.3.0.CP06 will be released shortly and will contain the necessary bug fix.
+			</para>
+			<important>
+				<para>
+					For more information about this issue that may impact your production server see <xref linkend="Known_Issues_with_this_release"/>. 
+				</para>
+			</important>
 		</section>
 		<section id="JAX_WS">
 			<title>JBoss Web Services 2.0.1</title>
@@ -167,6 +175,14 @@
 	</section>
 	<section id="Important_Notes">
 		<title>Important Notes</title>
+		<para>
+			A known issue exists within the JBoss Messaging component that allows for duplicate message IDs to be generated and may cause production software issues. Enterprise Application Platform 4.3.0.CP06 will be released shortly and will contain the necessary bug fix.
+		</para>
+		<important>
+			<para>
+				For more information about this issue that may impact your production server see <xref linkend="Known_Issues_with_this_release"/>. 
+			</para>
+		</important>
 		<section id="Seam_Applications">
 			<title>
 				Running the example Seam Applications
@@ -1577,11 +1593,11 @@
 			<title>Documentation</title>
 			<para>
 				<itemizedlist>
-					<listitem>
+				<!--	<listitem>
 						<para>
 							<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-2059">JBPAPP-2059</ulink>: The <filename>JBoss Messaging User Guide</filename> has been updated with small additions throughout and a new final chapter that contains information on enabling the ordering group.
 						</para>
-					</listitem>
+					</listitem> -->
 					<listitem>
 						<para>
 							<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-2011">JBPAPP-2011</ulink>: Documentation which explains how to achieve POJO Endpoint authentication in this latest CP release, has been incorporated into the <filename>Server Configuration Guide</filename>. This information can be found in section <emphasis>10.13. POJO Endpoint Authentication and Authorization</emphasis>.
@@ -1808,6 +1824,19 @@
 				</itemizedlist>
 			</para>
 		</formalpara>
+		<formalpara>
+			<title>Messaging Known Issues</title>
+			<para>
+				<itemizedlist>
+					<listitem>
+						<para>
+							<ulink url="http://jira.jboss.com/jira/browse/JBMESSAGING-1682">JBMESSAGING-1682</ulink>: By increasing the allowed number of servers that are connected to a single host to 65535 in the <ulink url="http://jira.jboss.com/jira/browse/JBMESSAGING-1614">JBMESSAGING-1614</ulink> feature update, a unique key violation can occur. If the sending rate of messages within one node is equal to or greater than 32767 messages per millisecond (<varname>short.MAX_VALUE</varname>), and those messages are all stored in the database at the time,
+							this leads to a circumstance where two messages may have identical ID numbers. 
+						</para>
+					</listitem>
+				</itemizedlist>
+			</para>
+		</formalpara>
 	</section>
 <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Revision_History.xml"/>