[jboss-remoting-commits] JBoss Remoting SVN: r5058 - remoting2/branches/2.2/docs/guide/en.

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

Author: ron.sigal at jboss.com
Date: 2009-04-18 00:09:58 -0400 (Sat, 18 Apr 2009)
New Revision: 5058

Modified:
   remoting2/branches/2.2/docs/guide/en/chap5.xml
Log:
JBREM-1078: Removed references to MicroSocketClientInvoker.numberOfRetries.

Modified: remoting2/branches/2.2/docs/guide/en/chap5.xml
===================================================================
--- remoting2/branches/2.2/docs/guide/en/chap5.xml	2009-04-18 03:46:46 UTC (rev 5057)
+++ remoting2/branches/2.2/docs/guide/en/chap5.xml	2009-04-18 04:09:58 UTC (rev 5058)
@@ -1069,18 +1069,8 @@
       to the maximum number of concurrent client calls that can be made from
       the socket client invoker. The default is 50.</para>
 
-      <para><emphasis role="bold">numberOfRetries</emphasis> - number of
-      retries to get a socket from the pool. This basically equates to number
-      of seconds will wait to get client socket connection from pool before
-      timing out. If max retries is reached, will cause a
-      CannotConnectException to be thrown (whose cause will be SocketException
-      saying how long it waited for socket connection from pool). The default
-      is 30 (MAX_RETRIES)</para>
-
       <para><emphasis role="bold">numberOfCallRetries</emphasis> - number of
-      retries for making invocation. This is unrelated to numberOfRetries in
-      that when this comes into play is after it has already received a client
-      socket connection from the pool. However, is possible that the socket
+      retries for making invocation. It is possible that an existing socket
       connection timed out while waiting within the pool. Since not doing a
       connection check by default, will throw away the connection and try to
       get a new one. Will do this for whatever the numberOfCallRetries (which
@@ -1234,14 +1224,12 @@
         connection to the pool. As more client invocations are made, is
         possible for the number of socket connections to reach the maximum
         allowed (which is controlled by 'clientMaxPoolSize' property). At this
-        point, when the next client invocation is made, it will keep trying to
-        get an available connection from the pool, waiting 1 second in between
-        tries for up to maximum number of retries (which is controlled by the
-        numberOfRetries property). If runs out of retries, will throw
-        SocketException saying how long it waited to find available socket
-        connection.</para>
+        point, when the next client invocation is made, it will wait up to
+        30 seconds for an existing connection to be returned to the pool.
+        If it doesn't get a connection within 30 seconds, it will throw
+        an IllegalStateException.</para>
 
-        <para>Once the socket client invoker goes get an available socket
+        <para>Once the socket client invoker goes and get an available socket
         connection from the pool, are not out of the woods yet. There is still
         a possibility that the socket connection returned, while still
         appearing to be valid, has timed out while sitting in the pool. So if