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

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

Author: ron.sigal at jboss.com
Date: 2011-03-22 18:46:43 -0400 (Tue, 22 Mar 2011)
New Revision: 6298

Modified:
   remoting2/branches/2.x/docs/userguide/en/chap4.xml
   remoting2/branches/2.x/docs/userguide/en/chap5.xml
Log:
JBREM-1277: Added references to "acceptThreadPriorityIncrement" parameter.


Modified: remoting2/branches/2.x/docs/userguide/en/chap4.xml
===================================================================
--- remoting2/branches/2.x/docs/userguide/en/chap4.xml	2011-03-22 19:53:11 UTC (rev 6297)
+++ remoting2/branches/2.x/docs/userguide/en/chap4.xml	2011-03-22 22:46:43 UTC (rev 6298)
@@ -44,6 +44,15 @@
    <section>
    <title>Server side parameters</title>
    
+   <para><emphasis role="bold">acceptThreadPriorityIncrement</emphasis> - can
+   be used to increment the priority of the accept thread, which manages the
+   <classname>ServerSocket</classname>.  The value is added to
+   <code>java.lang.Thread.NORM_PRIORITY</code>, and the resulting value must be
+   no more than <code>java.lang.Thread.MAX_PRIORITY</code>.  This parameter might
+   be useful on a heavily loaded machine if the accept
+   thread is getting starved. Introduced in release 2.5.4.SP2.
+   </para>
+    
    <para><emphasis role="bold">backlog</emphasis> - the preferred number of
    unaccepted incoming connections allowed at a given time. The actual
    number may be greater than the specified backlog. When the queue is

Modified: remoting2/branches/2.x/docs/userguide/en/chap5.xml
===================================================================
--- remoting2/branches/2.x/docs/userguide/en/chap5.xml	2011-03-22 19:53:11 UTC (rev 6297)
+++ remoting2/branches/2.x/docs/userguide/en/chap5.xml	2011-03-22 22:46:43 UTC (rev 6298)
@@ -46,6 +46,15 @@
    <section>
    <title>Server side parameters</title>
    
+   <para><emphasis role="bold">acceptThreadPriorityIncrement</emphasis> - can
+   be used to increment the priority of the thread which manages the secondary
+   <classname>ServerSocket</classname> (as well as the thread that manages the primary
+   <classname>ServerSocket</classname> in the socket transport).  The value is added to
+   <code>java.lang.Thread.NORM_PRIORITY</code>, and the resulting value must be
+   no more than <code>java.lang.Thread.MAX_PRIORITY</code>.  This parameter might
+   be useful on a heavily loaded machine if the accept
+   thread is getting starved. Introduced in release 2.5.4.SP2.</para>
+   
    <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>