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

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

Author: ron.sigal at jboss.com
Date: 2011-03-22 15:53:11 -0400 (Tue, 22 Mar 2011)
New Revision: 6297

Modified:
   remoting2/branches/2.2/docs/guide/en/chap5.xml
Log:
JBREM-1277: Added discussion of "acceptThreadPriorityIncrement" parameter.


Modified: remoting2/branches/2.2/docs/guide/en/chap5.xml
===================================================================
--- remoting2/branches/2.2/docs/guide/en/chap5.xml	2011-03-22 19:42:23 UTC (rev 6296)
+++ remoting2/branches/2.2/docs/guide/en/chap5.xml	2011-03-22 19:53:11 UTC (rev 6297)
@@ -1078,6 +1078,16 @@
       <classname>java.net.SocketTimeoutException</classname>. If set to "true",
       or if JBossSerialization is being used, the server thread will continue to wait for an invocation; otherwise, it
       will return itself to the thread pool.</para>
+      
+         
+      <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.
+      </para>
         
       <bridgehead>Configurations affecting the Socket invoker
       client</bridgehead>
@@ -2847,6 +2857,18 @@
           <classname>BisocketServerInvoker</classname> uses it to govern the
           number of attempts it should make to create both ordinary and control
           sockets. The default value is 10. </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
+          <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 secondary <classname>ServerSocket</classname>
+          thread is getting starved.
+        </para>
+        
       </section>
       
       <section>
@@ -6821,6 +6843,18 @@
     value is 'serverSocketClass') - specifies the fully qualified class name
     for the custom SocketWrapper implementation to use on the server.</para>
   
+        
+    <para><emphasis role="bold">Bean properties (meaning have getter/setter):</emphasis></para>
+
+    <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.
+    </para>
+    
     <bridgehead>org.jboss.remoting.transport.socket.SocketWrapper</bridgehead>
 
     <para><emphasis role="bold">WRITE_TIMEOUT</emphasis> (actual value