[jboss-cvs] JBossRemoting/docs/guide/en ...

[Tom Elrod]

  User: telrod  
  Date: 06/11/03 14:12:48

  Modified:    docs/guide/en  chap5.xml
  Log:
  JBREM-607 - adding to doc the idleTimeout config setting
  
  Revision  Changes    Path
  1.13      +34 -10    JBossRemoting/docs/guide/en/chap5.xml
  
  (In the diff below, changes in quantity of whitespace are not shown.)
  
  Index: chap5.xml
  ===================================================================
  RCS file: /cvsroot/jboss/JBossRemoting/docs/guide/en/chap5.xml,v
  retrieving revision 1.12
  retrieving revision 1.13
  diff -u -b -r1.12 -r1.13
  --- chap5.xml	22 Sep 2006 05:51:28 -0000	1.12
  +++ chap5.xml	3 Nov 2006 19:12:48 -0000	1.13
  @@ -934,6 +934,16 @@
         and then back from the server. This config needs to be set on both
         client and server to work. This if false by default.</para>
   
  +      <para><emphasis role="bold">idleTimeout</emphasis> - indicates the
  +      number of seconds a pooled server thread can be idle (meaning time since
  +      last invocations request processed) before it should be cleaned up and
  +      removed from the thread pool. The value for this property must be
  +      greater than zero in order to enable idle timeouts on pooled server
  +      threads (otherwise they will not be checked). Setting to value less than
  +      zero will disable idle timeout checks on pooled server threads, in the
  +      case was previously enabled. The default value for this property is
  +      -1.</para>
  +
         <bridgehead>Configurations affecting the Socket invoker
         client</bridgehead>
   
  @@ -1079,6 +1089,20 @@
           then they will be processed (of course this is a request by request
           determination).</para>
   
  +        <para>As of JBossRemoting 2.2.0 release, can also add configuration
  +        for cleaning up idle server threads using the 'idleTimeout'
  +        configuration property. Setting this property to a value of greater
  +        than zero will activate idle timeout checking, which is disabled by
  +        default. When enabled, the idle timeout checker will periodically
  +        iterate through the server threads that are active and inactive and if
  +        have not processed a request within the designated idle timeout
  +        period, the server thread will be shutdown and removed from
  +        corresponding pool. Active server threads are ones that have a socket
  +        connection associated with it and are in a blocked read waiting for
  +        data from the client. Inactive server threads are ones that have
  +        finished processing on a particular socket connection and have been
  +        returned to the thread pool for later reuse. </para>
  +
           <bridgehead>client</bridgehead>
   
           <para>When the socket client invoker makes its first invocation, it