[jboss-remoting-commits] JBoss Remoting SVN: r6362 - remoting2/branches/2.x/docs/userguide/en.

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

Author: ron.sigal at jboss.com
Date: 2011-05-05 21:49:37 -0400 (Thu, 05 May 2011)
New Revision: 6362

Modified:
   remoting2/branches/2.x/docs/userguide/en/chap5.xml
Log:
JBREM-1275: Added definition of bisocket "secondaryMaxThreads" and "secondaryTimeout" parameters.

Modified: remoting2/branches/2.x/docs/userguide/en/chap5.xml
===================================================================
--- remoting2/branches/2.x/docs/userguide/en/chap5.xml	2011-05-06 01:27:31 UTC (rev 6361)
+++ remoting2/branches/2.x/docs/userguide/en/chap5.xml	2011-05-06 01:49:37 UTC (rev 6362)
@@ -40,6 +40,9 @@
    failures.  Currently, the default values are accepted.  
    </para>
    
+   <para><emphasis role="bold">Note.</emphasis> If opening ports on the client side is not a problem,
+   then JBoss Messaging will run just fine with the somewhat simpler socket transport.</para>
+   
    <para>The following bisocket configuration parameters are added to those used in the socket transport:
    </para>
    
@@ -57,6 +60,14 @@
    
    <para><emphasis role="bold">pingFrequency</emphasis> - the frequency, in milliseconds, with which the server
    side sends a ping over the control connection. The default value is 5000 milliseconds.</para>
+      
+   <para><emphasis role="bold">secondaryMaxThreads</emphasis>: 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">secondaryTimeout</emphasis>: 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>