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

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

Author: irooskov at redhat.com
Date: 2009-01-15 00:47:49 -0500 (Thu, 15 Jan 2009)
New Revision: 82897

Modified:
   projects/docs/enterprise/4.3.4/readme/en-US/Release_Notes_CP04.xml
Log:
updated release notes with new JIRAs


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-15 05:28:44 UTC (rev 82896)
+++ projects/docs/enterprise/4.3.4/readme/en-US/Release_Notes_CP04.xml	2009-01-15 05:47:49 UTC (rev 82897)
@@ -351,24 +351,19 @@
 							</listitem>
 							<listitem>
 								<para>
-									
+									During occurances of the server being under heavy load, an <exceptionname>IllegalStateException</exceptionname> would occur within the <methodname>ConnectorValidator.run()</methodname> method because further synchronization on the <varname>lock</varname> variable was necessary. This issue was fixed during the rectification of the above problem. 
 								</para>
 							</listitem>
 							<listitem>
 								<para>
-									
+									A synchronization error within the <classname>MarshalFactory</classname> was allowing a subsystem to add a marshaller at the same time as EJB3 was trying to extract one causing users to receive an <exceptionname>InvalidMarshallingResource</exceptionname> exception; this also applied to unmarshallers. The error has been fixed by updating the <filename>jboss-remoting.jar</filename> file to include synchronized static Maps within the <classname>MarshalFactory</classname>.
 								</para>
 							</listitem>
 							<listitem>
 								<para>
-									
+									The <classname>SocketServerInvoker</classname> had an issue when shutting down <varname>ServerThreads</varname> causing a user to possibly receive an invocation to a closed <classname>SocketServerInvoker</classname> on the client side, causing an <exceptionname>InvalidStateException</exceptionname>. Allowing this exception would cause a clustered EJB3 system to generate a <exceptionname>UndeclaredThrowableException</exceptionname> instead of trying alternative servers. To allow for alternatives to be attempted, an optional behavior of allowing the <classname>MicroRemoteClientInvoker</classname> to interpret an <exceptionname>InvalidStateException</exceptionname> as a <exceptionname>CannotConnectException</exceptionname>, allowing for other servers to be attempted.
 								</para>
 							</listitem>
-							<listitem>
-								<para>
-									
-								</para>
-							</listitem>
 						</itemizedlist>
 					</listitem>
 				</itemizedlist>