JBoss Remoting SVN: r5045 - remoting2/branches/2.x/docs/guide/en.
by jboss-remoting-commits＠lists.jboss.org
Author: ron.sigal(a)jboss.com
Date: 2009-04-15 02:01:51 -0400 (Wed, 15 Apr 2009)
New Revision: 5045
Modified:
remoting2/branches/2.x/docs/guide/en/chap17.xml
Log:
JBREM-1118: Added release notes for 2.5.1.
Modified: remoting2/branches/2.x/docs/guide/en/chap17.xml
===================================================================
--- remoting2/branches/2.x/docs/guide/en/chap17.xml 2009-04-15 05:40:09 UTC (rev 5044)
+++ remoting2/branches/2.x/docs/guide/en/chap17.xml 2009-04-15 06:01:51 UTC (rev 5045)
@@ -69,7 +69,47 @@
<section>
<title>Version 2.5</title>
+
+ <bridgehead>Release Notes - JBoss Remoting - Version 2.5.1 (Flounder)</bridgehead>
+ <para><emphasis role="bold">Bug</emphasis></para>
+
+ <para>* [JBREM-992] - Can't restart a Connector that uses SocketServerInvoker</para>
+ <para>* [JBREM-1069] - Make ConnectorValidator configure ping period correctly</para>
+ <para>* [JBREM-1070] - Fix deadlock in ConnectionValidator</para>
+ <para>* [JBREM-1071] - IllegalStateException in ConnectorValidator.run()</para>
+ <para>* [JBREM-1072] - Synchronize access to static maps in MarshalFactory</para>
+ <para>* [JBREM-1076] - SocketServerInvoker.processInvocation() should return if running == false</para>
+ <para>* [JBREM-1081] - Fix NPE in ServerInvokerCallbackHandler </para>
+ <para>* [JBREM-1083] - Each Client creates a new invokerDestructionTimer</para>
+ <para>* [JBREM-1088] - MicroSocketClientInvoker(InvokerLocator locator, Map configuration) ctor - not propagating exceptions (only message is wrapped)</para>
+ <para>* [JBREM-1099] - Make MulticastDetector detection message send buffer size configurable</para>
+ <para>* [JBREM-1109] - Eliminate race in MicroRemoteClientInvoker.getDataType()</para>
+ <para>* [JBREM-1111] - CLONE [JBREM-851] - In LeasePinger replace Timer if it has shut down</para>
+ <para>* [JBREM-1112] - Potential race between ConnectionValidator and ConnectionListener upon connection failure</para>
+ <para>* [JBREM-1113] - ServerInvokerCallbackHandlers leak when client doesn't shut down </para>
+
+ <para><emphasis role="bold">Feature request</emphasis></para>
+ <para>* [JBREM-1082] - Allow ConnectionValidator to access InvokerLocator parameters</para>
+ <para>* [JBREM-1084] - Allow CallbackPoller to access Client and InvokerLocator parameters</para>
+ <para>* [JBREM-1102] - Make configuration map available to MarshalFactory</para>
+ <para>* [JBREM-1114] - Update servlet transport to support JBossMessaging</para>
+
+ <para><emphasis role="bold">Release</emphasis></para>
+
+ <para>* [JBREM-1118] - Release 2.5.1</para>
+
+ <para><emphasis role="bold">Task</emphasis></para>
+
+ <para>* [JBREM-139] - need automated test for servlet server invoker</para>
+ <para>* [JBREM-1085] - Reduce log level of ServerSocketWrapper.close() log messages</para>
+ <para>* [JBREM-1103] - correct javadoc for Client.invokeOneway()</para>
+ <para>* [JBREM-1104] - Identity.get() should create a more meaningful RuntimeException message</para>
+ <para>* [JBREM-1108] - Warn against making ConnectionValidator.validatorPingPeriod shorter than ConnectionValidator.validatorPingTimeout</para>
+ <para>* [JBREM-1110] - InvokerLocator.getParameters() should not return null</para>
+ <para>* [JBREM-1115] - Update jars to match AS 5.1.0.CR1</para>
+ <para>* [JBREM-1117] - Assure version compatibility with earlier versions of Remoting</para>
+
<bridgehead>Release Notes - JBoss Remoting - Version 2.5.0.SP2 (Flounder)</bridgehead>
<para><emphasis role="bold">Bug</emphasis></para>
15 years
JBoss Remoting SVN: r5044 - remoting2/branches/2.x/docs/guide/en.
by jboss-remoting-commits＠lists.jboss.org
Author: ron.sigal(a)jboss.com
Date: 2009-04-15 01:40:09 -0400 (Wed, 15 Apr 2009)
New Revision: 5044
Modified:
remoting2/branches/2.x/docs/guide/en/chap1.xml
Log:
JBREM-1118: Added section for release 2.5.1.
Modified: remoting2/branches/2.x/docs/guide/en/chap1.xml
===================================================================
--- remoting2/branches/2.x/docs/guide/en/chap1.xml 2009-04-15 05:31:11 UTC (rev 5043)
+++ remoting2/branches/2.x/docs/guide/en/chap1.xml 2009-04-15 05:40:09 UTC (rev 5044)
@@ -189,6 +189,24 @@
support jdk 1.4.</para>
<section>
+ <title>Release 2.5.1</title>
+ <itemizedlist>
+ <listitem>
+ <para>Security fix (JBREM-1116 "Remove SecurityUtility")</para>
+ </listitem>
+ <listitem>
+ <para>More flexible configuration (see <code>org.jboss.remoting.Client.USE_ALL_PARAMS</code>)</para>
+ </listitem>
+ <listitem>
+ <para>Jars updated to conform to Application Server 5.1.0.CR1</para>
+ </listitem>
+ <listitem>
+ <para>Multiple bug fixes.</para>
+ </listitem>
+ </itemizedlist>
+ </section>
+
+ <section>
<title>Release 2.5.0.SP2</title>
<itemizedlist>
<listitem>
15 years
JBoss Remoting SVN: r5043 - remoting2/branches/2.x/docs/guide/en.
by jboss-remoting-commits＠lists.jboss.org
Author: ron.sigal(a)jboss.com
Date: 2009-04-15 01:31:11 -0400 (Wed, 15 Apr 2009)
New Revision: 5043
Modified:
remoting2/branches/2.x/docs/guide/en/master.xml
Log:
JBREM-1118: Updated version and release date.
Modified: remoting2/branches/2.x/docs/guide/en/master.xml
===================================================================
--- remoting2/branches/2.x/docs/guide/en/master.xml 2009-04-15 05:29:29 UTC (rev 5042)
+++ remoting2/branches/2.x/docs/guide/en/master.xml 2009-04-15 05:31:11 UTC (rev 5043)
@@ -24,9 +24,9 @@
<bookinfo>
<title>JBoss Remoting Guide</title>
- <subtitle>JBoss Remoting version 2.5.0.SP2</subtitle>
+ <subtitle>JBoss Remoting version 2.5.1</subtitle>
- <releaseinfo>November 20, 2008</releaseinfo>
+ <releaseinfo>April 15, 2009</releaseinfo>
<mediaobject>
<imageobject>
15 years
JBoss Remoting SVN: r5042 - remoting2/branches/2.x/docs/guide/en.
by jboss-remoting-commits＠lists.jboss.org
Author: ron.sigal(a)jboss.com
Date: 2009-04-15 01:29:29 -0400 (Wed, 15 Apr 2009)
New Revision: 5042
Modified:
remoting2/branches/2.x/docs/guide/en/chap5.xml
Log:
JBREM-1113: Added discussion of ServerInvokerCallbackHandler.shutdown().
Modified: remoting2/branches/2.x/docs/guide/en/chap5.xml
===================================================================
--- remoting2/branches/2.x/docs/guide/en/chap5.xml 2009-04-15 05:13:38 UTC (rev 5041)
+++ remoting2/branches/2.x/docs/guide/en/chap5.xml 2009-04-15 05:29:29 UTC (rev 5042)
@@ -2786,6 +2786,16 @@
</para>
<para>
+ <emphasis role="bold">Note.</emphasis> As of release 2.5.1,
+ <classname>ServerInvokerCallbackHandler</classname>
+ has a new method, <methodname>shutdown()</methodname>, which can be used by, for example, the
+ <classname>ServerInvocationHandler</classname> with which it is registered, or by an
+ <classname>org.jboss.remoting.ConnectionListener</classname> upon being informed of a
+ connection failure, to clean up the <classname>ServerInvokerCallbackHandler</classname>
+ and references thereto.
+ </para>
+
+ <para>
The client side of a callback connection is identified in one of two
ways, according to whether there is a callback
<classname>Connector</classname> associated with the connection. If
15 years
JBoss Remoting SVN: r5041 - remoting2/branches/2.2/docs/guide/en.
by jboss-remoting-commits＠lists.jboss.org
Author: ron.sigal(a)jboss.com
Date: 2009-04-15 01:13:38 -0400 (Wed, 15 Apr 2009)
New Revision: 5041
Modified:
remoting2/branches/2.2/docs/guide/en/chap5.xml
Log:
JBREM-1084: Added discussion of Client.USE_ALL_PARAMS.
Modified: remoting2/branches/2.2/docs/guide/en/chap5.xml
===================================================================
--- remoting2/branches/2.2/docs/guide/en/chap5.xml 2009-04-15 05:13:04 UTC (rev 5040)
+++ remoting2/branches/2.2/docs/guide/en/chap5.xml 2009-04-15 05:13:38 UTC (rev 5041)
@@ -3712,6 +3712,15 @@
<methodname>addListener()</methodname>.
</para>
+ <para><emphasis role="bold">Note.</emphasis> Since release 2.2.2.SP12, if the first instance
+ of the parameter <code>org.jboss.remoting.Client.USE_ALL_PARAMS</code>
+ (actual value "useAllParams") found successively in the <classname>InvokerLocator</classname>, the
+ <classname>Client</classname>'s configuration map, or the metadata map is set
+ to "true", then polled callbacks can be configured by parameters in the
+ <classname>InvokerLocator</classname> and <classname>Client</classname>'s
+ configuration map as well as the metadata map passed to <methodname>addListener()</methodname>.
+ </para>
+
<para>
If the client is in an environment where the server is not allowed to
establish a network connection to the client (e.g. firewall rules
@@ -6005,6 +6014,14 @@
map passed to the Client constructor providing a ssl
javax.net.ssl.HandshakeCompletedListener implementation, which will be
called on when ssl handshake completed with server.</para>
+
+ <para><emphasis role="bold">USE_ALL_PARAMS</emphasis>
+ (actual value is 'useAllParameters') - used by
+ <classname>org.jboss.remoting.ConnectionValidator</classname> and
+ <classname>org.jboss.remoting.callback.CallbackPoller</classname> to
+ determine if configuration parameters should be retrieved from the
+ <classname>InvokerLocator</classname> or the
+ <classname>Client</classname>'s configuration map.</para>
<para></para>
15 years
JBoss Remoting SVN: r5040 - remoting2/branches/2.x/docs/guide/en.
by jboss-remoting-commits＠lists.jboss.org
Author: ron.sigal(a)jboss.com
Date: 2009-04-15 01:13:04 -0400 (Wed, 15 Apr 2009)
New Revision: 5040
Modified:
remoting2/branches/2.x/docs/guide/en/chap5.xml
Log:
JBREM-1084: Added discussion of Client.USE_ALL_PARAMS.
Modified: remoting2/branches/2.x/docs/guide/en/chap5.xml
===================================================================
--- remoting2/branches/2.x/docs/guide/en/chap5.xml 2009-04-15 04:37:16 UTC (rev 5039)
+++ remoting2/branches/2.x/docs/guide/en/chap5.xml 2009-04-15 05:13:04 UTC (rev 5040)
@@ -3316,6 +3316,15 @@
<methodname>addListener()</methodname>.
</para>
+ <para><emphasis role="bold">Note.</emphasis> Since release 2.5.1, if the first instance
+ of the parameter <code>org.jboss.remoting.Client.USE_ALL_PARAMS</code>
+ (actual value "useAllParams") found successively in the <classname>InvokerLocator</classname>, the
+ <classname>Client</classname>'s configuration map, or the metadata map is set
+ to "true", then polled callbacks can be configured by parameters in the
+ <classname>InvokerLocator</classname> and <classname>Client</classname>'s
+ configuration map as well as the metadata map passed to <methodname>addListener()</methodname>.
+ </para>
+
<para>
If the client is in an environment where the server is not allowed to
establish a network connection to the client (e.g. firewall rules
@@ -5807,6 +5816,14 @@
javax.net.ssl.HandshakeCompletedListener implementation, which will be
called on when ssl handshake completed with server.</para>
+ <para><emphasis role="bold">USE_ALL_PARAMS</emphasis>
+ (actual value is 'useAllParameters') - used by
+ <classname>org.jboss.remoting.ConnectionValidator</classname> and
+ <classname>org.jboss.remoting.callback.CallbackPoller</classname> to
+ determine if configuration parameters should be retrieved from the
+ <classname>InvokerLocator</classname> or the
+ <classname>Client</classname>'s configuration map.</para>
+
<para></para>
<para>The following three configuration properties are only useful when
15 years
JBoss Remoting SVN: r5039 - remoting2/branches/2.2/src/main/org/jboss/remoting/ident.
by jboss-remoting-commits＠lists.jboss.org
Author: ron.sigal(a)jboss.com
Date: 2009-04-15 00:37:16 -0400 (Wed, 15 Apr 2009)
New Revision: 5039
Modified:
remoting2/branches/2.2/src/main/org/jboss/remoting/ident/Identity.java
Log:
JBREM-1104: Ported David Lloyd's fix to 2.2 branch.
Modified: remoting2/branches/2.2/src/main/org/jboss/remoting/ident/Identity.java
===================================================================
--- remoting2/branches/2.2/src/main/org/jboss/remoting/ident/Identity.java 2009-04-15 02:00:56 UTC (rev 5038)
+++ remoting2/branches/2.2/src/main/org/jboss/remoting/ident/Identity.java 2009-04-15 04:37:16 UTC (rev 5039)
@@ -208,7 +208,10 @@
}
catch(Exception ex)
{
- throw new RuntimeException("Exception creating identity: " + ex.getMessage());
+ String type = ex.getClass().getName();
+ final RuntimeException rex = new RuntimeException("Exception creating identity: " + type + ": " + ex.getMessage());
+ rex.setStackTrace(ex.getStackTrace());
+ throw rex;
}
}
15 years
JBoss Remoting SVN: r5038 - remoting2/branches/2.2/src/main/org/jboss/remoting/transport/socket.
by jboss-remoting-commits＠lists.jboss.org
Author: ron.sigal(a)jboss.com
Date: 2009-04-14 22:00:56 -0400 (Tue, 14 Apr 2009)
New Revision: 5038
Modified:
remoting2/branches/2.2/src/main/org/jboss/remoting/transport/socket/MicroSocketClientInvoker.java
Log:
JBREM-1088: Added original exception as RuntimeException cause.
Modified: remoting2/branches/2.2/src/main/org/jboss/remoting/transport/socket/MicroSocketClientInvoker.java
===================================================================
--- remoting2/branches/2.2/src/main/org/jboss/remoting/transport/socket/MicroSocketClientInvoker.java 2009-04-15 01:59:44 UTC (rev 5037)
+++ remoting2/branches/2.2/src/main/org/jboss/remoting/transport/socket/MicroSocketClientInvoker.java 2009-04-15 02:00:56 UTC (rev 5038)
@@ -255,7 +255,7 @@
catch (Exception ex)
{
log.error("Error setting up " + this, ex);
- throw new RuntimeException(ex.getMessage());
+ throw new RuntimeException(ex.getMessage(), ex);
}
log.debug(this + " constructed");
15 years
JBoss Remoting SVN: r5037 - remoting2/branches/2.x/src/main/org/jboss/remoting/transport/socket.
by jboss-remoting-commits＠lists.jboss.org
Author: ron.sigal(a)jboss.com
Date: 2009-04-14 21:59:44 -0400 (Tue, 14 Apr 2009)
New Revision: 5037
Modified:
remoting2/branches/2.x/src/main/org/jboss/remoting/transport/socket/MicroSocketClientInvoker.java
Log:
JBREM-1088: Added original exception as RuntimeException cause.
Modified: remoting2/branches/2.x/src/main/org/jboss/remoting/transport/socket/MicroSocketClientInvoker.java
===================================================================
--- remoting2/branches/2.x/src/main/org/jboss/remoting/transport/socket/MicroSocketClientInvoker.java 2009-04-15 01:31:36 UTC (rev 5036)
+++ remoting2/branches/2.x/src/main/org/jboss/remoting/transport/socket/MicroSocketClientInvoker.java 2009-04-15 01:59:44 UTC (rev 5037)
@@ -277,7 +277,7 @@
catch (Exception ex)
{
log.debug("Error setting up " + this, ex);
- throw new RuntimeException(ex.getMessage());
+ throw new RuntimeException(ex.getMessage(), ex);
}
log.debug(this + " constructed");
15 years
JBoss Remoting SVN: r5036 - remoting2/branches/2.2/docs/guide/en.
by jboss-remoting-commits＠lists.jboss.org
Author: ron.sigal(a)jboss.com
Date: 2009-04-14 21:31:36 -0400 (Tue, 14 Apr 2009)
New Revision: 5036
Modified:
remoting2/branches/2.2/docs/guide/en/chap8.xml
Log:
JBREM-1082: Added reference to Client.USE_ALL_PARAMETERS; (2) JBREM-1112: added reference to FAILURE_DISCONNECT_TIMEOUT; (3) JBREM-1108: noted validatorPingPeriod should be longer than validatorPingTimeout.
Modified: remoting2/branches/2.2/docs/guide/en/chap8.xml
===================================================================
--- remoting2/branches/2.2/docs/guide/en/chap8.xml 2009-04-15 01:30:20 UTC (rev 5035)
+++ remoting2/branches/2.2/docs/guide/en/chap8.xml 2009-04-15 01:31:36 UTC (rev 5036)
@@ -57,13 +57,46 @@
"validatorPingTimeout") - specifies the time, in milliseconds, allowed for
arrival of a response to a PING message. The default value is 1000.</para>
- <para>For more configuration parameters, see <xref
- linkend="section-interactions"/>.</para>
+ <para><emphasis role="bold">FAILURE_DISCONNECT_TIMEOUT</emphasis> (actual value
+ "failureDisconnectTimeout") - if the parameter "stopLeaseOnFailure"
+ (see <xref linkend="section-interactions"/>) is set to
+ "true", then "failureDisconnectTimeout" determines the disconnect timeout value
+ to be used by <classname>org.jboss.remoting.LeasePinger</classname> in shutting
+ down. In particular, if "failureDisconnectTimeout" is set to "0", then
+ <classname>LeasePinger</classname> will avoid any network i/o.</para>
- <para>Note, also, that <classname>ConnectionValidator</classname> creates a
+ <para> Normally, the values for these parameters are obtained either from
+ the <classname>Client</classname>'s configuration map or the metadata map
+ passed to <methodname>addConnectionListener()</methodname>, with values in
+ the metadata map taking precedence. However, another relevant parameter is
+ defined in <classname>org.jboss.remoting.Client</classname>:</para>
+
+ <para><emphasis role="bold">USE_ALL_PARAMS</emphasis> (actual value
+ "useAllParams") - this parameter is searched for in the
+ <classname>InvokerLocator</classname>, in the configuration map passed to
+ the <classname>Client</classname>, and in the metadata map (in that order).
+ If the last occurrence found is set to "true", then parameter values are
+ first obtained from the <classname>InvokerLocator</classname>, followed by
+ the <classname>Client</classname>'s configuration map and the
+ metadata map.</para>
+
+ <para>Note that <classname>ConnectionValidator</classname> creates a
client invoker to sends the PING messages, and it passes the metadata map to
configure the client invoker.</para>
+ <para><emphasis role="bold">NOTE.</emphasis> The default values of VALIDATOR_PING_PERIOD
+ and VALIDATOR_PING_TIMEOUT have often been found in practice to be too small, increasing
+ the likelihood of spurious connection failures.</para>
+
+ <para><emphasis role="bold">NOTE.</emphasis> It is important to set VALIDATOR_PING_PERIOD
+ to a value greater than the value of VALIDATOR_PING_TIMEOUT. Doing so gives the
+ <classname>ConnectionValidator</classname> a chance to notify all
+ <classname>ConnectionListener</classname>s, which might result in shutting down the
+ connection, before the next PING is sent.</para>
+
+ <para>For more configuration parameters, see <xref
+ linkend="section-interactions"/>.</para>
+
</section>
<section id="section-server-side" xreflabel="Server side monitoring">
@@ -94,7 +127,7 @@
<programlisting>public void addConnectionListener(ConnectionListener listener)</programlisting>
- <para>or though the use of the
+ <para>or through the use of the
<code>ServerInvoker.CONNECTION_LISTENER</code> parameter (actual value
"connectionListener") in the <classname>Connector</classname>'s
configuration map or XML configuration file. Once both criteria are met, the
15 years