[jboss-cvs] JBossAS SVN: r83221 - in projects/docs/enterprise: 4.3.4/Getting_Started/en-US and 1 other directories.

jboss-cvs-commits at lists.jboss.org jboss-cvs-commits at lists.jboss.org
Wed Jan 21 22:33:42 EST 2009


Author: irooskov at redhat.com
Date: 2009-01-21 22:33:41 -0500 (Wed, 21 Jan 2009)
New Revision: 83221

Modified:
   projects/docs/enterprise/4.2.6/readme/en-US/Release_Notes_CP06.xml
   projects/docs/enterprise/4.3.4/Getting_Started/en-US/Start_Stop_Server.xml
   projects/docs/enterprise/4.3.4/readme/en-US/Release_Notes_CP04.xml
Log:
update documentation for next Cp releases


Modified: projects/docs/enterprise/4.2.6/readme/en-US/Release_Notes_CP06.xml
===================================================================
--- projects/docs/enterprise/4.2.6/readme/en-US/Release_Notes_CP06.xml	2009-01-22 03:02:28 UTC (rev 83220)
+++ projects/docs/enterprise/4.2.6/readme/en-US/Release_Notes_CP06.xml	2009-01-22 03:33:41 UTC (rev 83221)
@@ -43,6 +43,94 @@
 			</para>
 		</section>
 	</section> -->
+	<section id="Component_Versions">
+		<title>Component Versions</title>
+		<para>
+			This section details the versions of the components which create the Enterprise Application Platform 4.3 that can be found in this Cumulative Patch release.
+		</para>
+		<itemizedlist>
+			<listitem>
+				<para>
+					JBoss Application Server 4.2.z
+				</para>
+			</listitem>
+			<listitem>
+				<para>
+					Hibernate 3.2.4.SP1.CP07
+				</para>
+			</listitem>
+			<listitem>
+				<para>
+					Hibernate Annotations 3.2.1.GA.CP04
+				</para>
+			</listitem>
+			<listitem>
+				<para>
+					Hibernate Entity Manager 3.2.1.GA_CP05
+				</para>
+			</listitem>
+			<listitem>
+				<para>
+					JAF 1.2_10
+				</para>
+			</listitem>
+			<listitem>
+				<para>
+					JBoss Cache 1.4.1.SP11
+				</para>
+			</listitem>
+			<listitem>
+				<para>
+					JBoss JAXR 1.2.0.SP2
+				</para>
+			</listitem>
+			<listitem>
+				<para>
+					JBoss Remoting 2.2.2.SP11
+				</para>
+			</listitem>
+			<listitem>
+				<para>
+					JBoss Transactions 4.2.3.SP5.CP03
+				</para>
+			</listitem>
+			<listitem>
+				<para>
+					JBoss Web 2.0.0-6.CP09
+				</para>
+			</listitem>
+			<listitem>
+				<para>
+					JBoss Web Services 1.2.1.GA_CP04
+				</para>
+			</listitem>
+			<listitem>
+				<para>
+					JGroups 2.4.5
+				</para>
+			</listitem>
+			<listitem>
+				<para>
+					JSF 1.2_10
+				</para>
+			</listitem>
+			<listitem>
+				<para>
+					Seam 1.2.1.AP
+				</para>
+			</listitem>
+			<listitem>
+				<para>
+					Xalan 2.7.0.patch02
+				</para>
+			</listitem>
+		</itemizedlist>
+		<note>
+			<para>
+				The Enterprise Application Platform Server has been redefined for the enterprise market to a level where direct association to a community release can no longer be drawn.
+			</para>
+		</note>
+	</section>
 	<section id="Installation_Notes">
 		<title>Installation and Migration Notes</title>
 		<para>
@@ -582,6 +670,11 @@
 				<itemizedlist>
 					<listitem>
 						<para>
+							<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1635">JBPAPP-1635</ulink>: The <classname>OracleExceptionSorter</classname> has been enhanced for this release with new error codes of 17002 (connection reset) and 17008 (connection closed) now able to be handled. These enhancements have been applied to the <filename>OracleExceptionSorter.java</filename> file.
+						</para>
+					</listitem>
+					<listitem>
+						<para>
 							<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1540">JBPAPP-1540</ulink>: Within the cluster section of the EAP, the <classname>GossipRouter</classname> and <classname>GossipClient</classname> (TCPGOSSIP) did not have socket read timeouts, socket linger timeouts and backlog set to provide the best behaviour when heavily utilized or under network situations in need of improvement. This fix provides default values and configuration options for these in order to avoid problematic situations. 
 						</para>
 					</listitem>

Modified: projects/docs/enterprise/4.3.4/Getting_Started/en-US/Start_Stop_Server.xml
===================================================================
--- projects/docs/enterprise/4.3.4/Getting_Started/en-US/Start_Stop_Server.xml	2009-01-22 03:02:28 UTC (rev 83220)
+++ projects/docs/enterprise/4.3.4/Getting_Started/en-US/Start_Stop_Server.xml	2009-01-22 03:33:41 UTC (rev 83221)
@@ -120,7 +120,6 @@
 			Using the shutdown command requires a server configuration that contains the <literal>jmx-invoker-service.xml</literal> service. Hence you cannot use the shutdown command with the <literal>minimal</literal> configuration.
 		</para>
 	</section>
-	
 	<section id="Starting_and_Stopping_the_Server-Running_as_a_Service_under_Microsoft_Windows">
 		<title> Running as a Service under Microsoft Windows </title>
 		<para>
@@ -240,5 +239,31 @@
 			</para>
 		</note>
 	</section>
+	<section>
+		<title>Starting Remote Connectivity to the JBoss Server</title>
+		<para>
+			In older versions of the JBoss Server, JBoss always bound to the address 0.0.0.0; creating an unprotected instance of JBoss. This is no longer the case, however there may arise a need for an unprotected instance and in order to instruct this behavior, the <code>-b</code> option must be used.
+		</para>
+		<para>
+			This option configures the <varname>jboss.bind.address</varname> to the JBoss startup script and setting the address to 0.0.0.0 permits JBoss to listen for connections on all IP addresses of the machine.
+		</para>
+		<para>
+			In order to execute this under Linux run:
+		</para>
+<programlisting>
+./run.sh -b 0.0.0.0
+</programlisting>
+		<para>
+			In order to execute this under Windows run:
+		</para>
+<programlisting>
+run.bat -b 0.0.0.0
+</programlisting>
+		<note>
+			<para>
+				Passing <code>-Djboss.bind.address</code> to the Java process as part of the <varname>JAVA_OPTS</varname> variable in the run scripts will not work, as the <code>-b</code> option should be utilized. The equivalent of the <code>-b</code> option however is <code>-Djboss.bind.address -Djava.rmi.server.hostname -Djgroups.bind_addr -Dbind.address</code>.
+			</para>
+		</note>
+	</section>
 </section>
 

Modified: projects/docs/enterprise/4.3.4/readme/en-US/Release_Notes_CP04.xml
===================================================================
--- projects/docs/enterprise/4.3.4/readme/en-US/Release_Notes_CP04.xml	2009-01-22 03:02:28 UTC (rev 83220)
+++ projects/docs/enterprise/4.3.4/readme/en-US/Release_Notes_CP04.xml	2009-01-22 03:33:41 UTC (rev 83221)
@@ -106,6 +106,11 @@
 			</listitem>
 			<listitem>
 				<para>
+					JBoss Web Services 2.0.1.SP2_CP05
+				</para>
+			</listitem>
+			<listitem>
+				<para>
 					JGroups 2.4.5
 				</para>
 			</listitem>
@@ -116,6 +121,11 @@
 			</listitem>
 			<listitem>
 				<para>
+					Seam 1.2.1.AP
+				</para>
+			</listitem>
+			<listitem>
+				<para>
 					Xalan 2.7.0.patch02
 				</para>
 			</listitem>
@@ -743,11 +753,11 @@
 			<title>Documentation</title>
 			<para>
 				<itemizedlist>
-					<listitem>
+				<!--	<listitem>
 						<para>
-							<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-">JBPAPP-</ulink>:
+							<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1472">JBPAPP-1472</ulink>: The instructions for adding SSL to EJB 2.1 were incorrect as they did not include code pertaining to marshalling. The appropriate code has now been added to the instructions in section 
 						</para>
-					</listitem>
+					</listitem> -->
 				</itemizedlist>
 			</para>
 		</formalpara>
@@ -757,6 +767,11 @@
 				<itemizedlist>
 					<listitem>
 						<para>
+							<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1635">JBPAPP-1635</ulink>: The <classname>OracleExceptionSorter</classname> has been enhanced for this release with new error codes of 17002 (connection reset) and 17008 (connection closed) now able to be handled. These enhancements have been applied to the <filename>OracleExceptionSorter.java</filename> file.
+						</para>
+					</listitem>
+					<listitem>
+						<para>
 							<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1540">JBPAPP-1540</ulink>: Within the cluster section of the EAP, the <classname>GossipRouter</classname> and <classname>GossipClient</classname> (TCPGOSSIP) did not have socket read timeouts, socket linger timeouts and backlog set to provide the best behaviour when heavily utilized or under network situations in need of improvement. This fix provides default values and configuration options for these in order to avoid problematic situations. 
 						</para>
 					</listitem>




More information about the jboss-cvs-commits mailing list