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

jboss-cvs-commits at lists.jboss.org jboss-cvs-commits at lists.jboss.org
Mon Jun 1 00:37:47 EDT 2009


Author: irooskov at redhat.com
Date: 2009-06-01 00:37:45 -0400 (Mon, 01 Jun 2009)
New Revision: 89581

Modified:
   projects/docs/enterprise/4.3.5/readme/en-US/Release_Notes_CP05.xml
Log:
updated release notes with new JIRA


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-06-01 03:03:06 UTC (rev 89580)
+++ projects/docs/enterprise/4.3.5/readme/en-US/Release_Notes_CP05.xml	2009-06-01 04:37:45 UTC (rev 89581)
@@ -489,7 +489,7 @@
 							</listitem>
 							<listitem>
 								<para>
-									<ulink url="http://jira.jboss.com/jira/browse/JBREM-1128">JBREM-1128</ulink>: 
+									<ulink url="http://jira.jboss.com/jira/browse/JBREM-1128">JBREM-1128</ulink>: Connection identity for the <classname>LeasePinger</classname> and <classname>Lease</classname> pair has been added by setting the parameter <property>org.jboss.remoting.Remoting.USE_CLIENT_CONNECTION_IDENTITY</property> to <emphasis>true</emphasis>. JBoss Remoting then identifies a connection with a <classname>LeasePinger</classname> and <classname>Lease</classname> pair and a client participates in a connection when it is connected by way of the new method <methodname>connect(ConnectionListener listener, Map metadata)</methodname>. This method serves to connect the client to the server by way of a new or existing client invoker, and it also registers the <classname>ConnectionListener</classname> with the client's new or exiting <classname>ConnectionValidator</classname>, while also registering the <classname>ConnectionValidator</classname> with the client invoker's <classname>LeasePinge!
 r</classname>. Subsequently, if any <classname>ConnectionValidator</classname> registered with that <classname>LeasePinger</classname> detects a connection failure, it will (if the <property>stopLeaseOnFailure</property> parameter is set to <emphasis>true</emphasis>) stop the <classname>LeasePinger</classname>, and the <classname>LeasePinger</classname> will cause each registered <classname>ConnectionValidator</classname> to notify each of its registered <classname>ConnectionListeners</classname> of the connection failure. If a client is reconnected by a call to the <methodname>Client.connect()</methodname> method, it will be associated with a new <classname>LeasePinger</classname> and be treated as a new connection.
 								</para>
 							</listitem>
 							<listitem>
@@ -525,11 +525,21 @@
 							</listitem>
 							<listitem>
 								<para>
+									<ulink url="http://jira.jboss.com/jira/browse/JBREM-1110">JBREM-1110</ulink>: The method <methodname>org.jboss.remoting.InvokerLocator.getParameters()</methodname> would return null if the URL had no paramerters. In this updated release, the method returns an empty <varname>Map</varname> instead to ensure safer execution.
+								</para>
+							</listitem>
+							<listitem>
+								<para>
 									<ulink url="http://jira.jboss.com/jira/browse/JBREM-1109">JBREM-1109</ulink>: Within the <methodname>org.jboss.remoting.MicroRemoteClientInvoker.getDataType()</methodname> method when the <varname>dataType</varname> variable was set to the value of the <methodname>getDataType(getLocator())</methodname> method, the variable would temporarily be set to null if the <classname>InvokerLocator</classname> had no datatype parameter. This caused issues because another thread may use the <varname>dataType</varname> variable and return a value of null. Correting this bug has lead to using a local variable called <varname>localDataType</varname> while a check occurs to see if <classname>InvokerLocator</classname> contains a datatype value. The number of threads has also been reduced to 1000 in order to avoid an <exceptionname>OutOfMemoryError</exceptionname> taht may have occured.
 								</para>
 							</listitem>
 							<listitem>
 								<para>
+									<ulink url="http://jira.jboss.com/jira/browse/JBREM-1104">JBREM-1104</ulink>: When the <methodname>org.jboss.remoting.ident.Identity.get()</methodname> method would fail in a call to <methodname>InetAddress.getLocalHost()</methodname>, the runtime exception <exceptionname>java.lang.RuntimeException: Exception creating identity: myhost: myhost</exceptionname> would be generated. The issue was that the exception message did not give any information to the user concerning the underlying problem relating to the host name. This output has been fixed to display to the user the correct information in relation to the main host name issue.
+								</para>
+							</listitem>
+							<listitem>
+								<para>
 									<ulink url="http://jira.jboss.com/jira/browse/JBREM-1102">JBREM-1102</ulink>: A feature was requested that would make the configuration map avaliable to the <classname>marshalFactory</classname>. In order to support this the new parameter <property>org.jboss.remoting.Remoting.PASS_CONFIG_MAP_TO_MARSHAL_FACTORY</property> has been added, which requires a setting of <emphasis>true</emphasis> in order to have the configuration map passed to the <classname>marshalFactory</classname>. If the parameter contains a value of <emphasis>false</emphasis> then the original behavior will be executed.
 								</para>
 							</listitem>
@@ -550,6 +560,11 @@
 							</listitem>
 							<listitem>
 								<para>
+									<ulink url="http://jira.jboss.com/jira/browse/JBREM-1085">JBREM-1085</ulink>: The log level of the <methodname>ServerSocketWrapper.close()</methodname> method log messages has been reduced in order to remove unwanted information. Instead of using the <methodname>log.debug()</methodname> call, the method now uses <methodname>log.trace()</methodname>.
+								</para>
+							</listitem>
+							<listitem>
+								<para>
 									<ulink url="http://jira.jboss.com/jira/browse/JBREM-1084">JBREM-1084</ulink>: When <methodname>org.jboss.remoting.Client.addConnectionListener()</methodname> created a <classname>CallbackPoller</classname>, a reference to itself and a metadata map would be passed. The issue arose from the <classname>CallbackPoller</classname> only accessing parameters in the metadata map. To rectify this issue the <property>Client.USE_ALL_PARAMS</property> parameter is checked within the <classname>InvokerLocator</classname>, the client's configuration map and the metadata map that is passed to the <methodname>Client.addListener()</methodname> method respectively. If the <property>useALLParams</property> property is found and set to a value of <emphasis>true</emphasis>, the <classname>InvokerLocator</classname>, the client's configuration map and the metadata map will be searched respectively for all parameters used by <classname>CallbackPoller</classname>, otherwise only the metad!
 ata map will be used, which is the default behavior.
 								</para>
 							</listitem>




More information about the jboss-cvs-commits mailing list