Author: ron.sigal(a)jboss.com
Date: 2011-05-05 21:11:12 -0400 (Thu, 05 May 2011)
New Revision: 6360
Modified:
remoting2/branches/2.x/docs/guide/en/chap5.xml
Log:
JBREM-1275: Added definition of bisocket "secondaryMaxThreads" and
"secondaryTimeout" parameters.
Modified: remoting2/branches/2.x/docs/guide/en/chap5.xml
===================================================================
--- remoting2/branches/2.x/docs/guide/en/chap5.xml 2011-05-05 04:48:41 UTC (rev 6359)
+++ remoting2/branches/2.x/docs/guide/en/chap5.xml 2011-05-06 01:11:12 UTC (rev 6360)
@@ -2493,7 +2493,22 @@
determine the connect ports used by the client side to connect to the
secondary <classname>ServerSocket</classname>s in a multihome
server.</para>
+
+ <para>
+ <emphasis role="bold">SECONDARY_MAX_THREADS</emphasis>
(actual value
+ is "secondaryMaxThreads"): Determines the maximum number of
+ sockets accepted by the secondary
<classname>ServerSocket</classname>
+ that can be processed simultaneously. Introduced in release
+ 2.5.4.SP2. Default value is 50.</para>
+ <para>
+ <emphasis role="bold">SECONDARY_TIMEOUT</emphasis>
(actual value
+ is "secondaryTimeout"): Determines the timeout used when reading
+ initial data from a socket accepted by the secondary
+ <classname>ServerSocket</classname>. Introduced in release
+ 2.5.4.SP2. Default value is 60000 ms.
+ </para>
+
<para>Also, the parameter "acceptThreadPriorityIncrement",
inherited from
<classname>org.jboss.remoting.transport.socket.SocketServerInvoker</classname>,
can
be used to increment the priority of the thread that manages the secondary
@@ -6590,7 +6605,22 @@
determine the connect ports used by the client side to connect to the
secondary <classname>ServerSocket</classname>s in a multihome
server.</para>
-
+
+ <para>
+ <emphasis role="bold">SECONDARY_MAX_THREADS</emphasis>
(actual value
+ is "secondaryMaxThreads"): Determines the maximum number of
+ sockets accepted by the secondary
<classname>ServerSocket</classname>
+ that can be processed simultaneously. Introduced in release
+ 2.5.4.SP2. Default value is 50.</para>
+
+ <para>
+ <emphasis role="bold">SECONDARY_TIMEOUT</emphasis>
(actual value
+ is "secondaryTimeout"): Determines the timeout used when reading
+ initial data from a socket accepted by the secondary
+ <classname>ServerSocket</classname>. Introduced in release
+ 2.5.4.SP2. Default value is 60000 ms.
+ </para>
+
</section>
<section>
Show replies by date