You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by re...@apache.org on 2003/07/29 18:40:37 UTC

cvs commit: jakarta-tomcat-catalina/webapps/docs/config coyote.xml jk2.xml

remm        2003/07/29 09:40:37

  Modified:    webapps/docs/config coyote.xml jk2.xml
  Log:
  - Update the connectors documentation.
  
  Revision  Changes    Path
  1.6       +26 -12    jakarta-tomcat-catalina/webapps/docs/config/coyote.xml
  
  Index: coyote.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-tomcat-catalina/webapps/docs/config/coyote.xml,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- coyote.xml	10 Feb 2003 19:36:44 -0000	1.5
  +++ coyote.xml	29 Jul 2003 16:40:36 -0000	1.6
  @@ -56,12 +56,6 @@
   
     <attributes>
   
  -    <attribute name="className" required="true">
  -      <p>Java class name of the implementation to use.  This class must
  -      implement the <code>org.apache.catalina.Connector</code> interface.
  -      You must specify the standard value defined below.</p>
  -    </attribute>
  -
       <attribute name="enableLookups" required="false">
         <p>Set to <code>true</code> if you want calls to
         <code>request.getRemoteHost()</code> to perform DNS lookups in
  @@ -166,18 +160,33 @@
         this attribute is set to "false".</p>
       </attribute>
   
  -    <attribute name="maxProcessors" required="false">
  +    <attribute name="maxKeepAliveRequests" required="false">
  +      <p>The maximum number of HTTP requests which can be pipelined until
  +      the connection is closed by the server. Setting this attribute to 1 will
  +      disable HTTP/1.0 keep-alive, as well as HTTP/1.1 keep-alive and 
  +      pipelining. If
  +      not specified, this attribute is set to 100.</p>
  +    </attribute>
  +
  +    <attribute name="maxSpareThreads" required="false">
  +      <p>The maximum number of unused request processing threads that 
  +      will be allowed to exist until the thread pool starts stopping the
  +      unnecessary threads.  The default value is 50.</p>
  +    </attribute>
  +
  +    <attribute name="maxThreads" required="false">
         <p>The maximum number of request processing threads to be created
         by this <strong>Connector</strong>, which therefore determines the
         maximum number of simultaneous requests that can be handled.  If
  -      not specified, this attribute is set to 20.</p>
  +      not specified, this attribute is set to 200.</p>
       </attribute>
   
  -    <attribute name="minProcessors" required="false">
  +    <attribute name="minSpareThreads" required="false">
         <p>The number of request processing threads that will be created
  -      when this <strong>Connector</strong> is first started.  This
  -      attribute should be set to a value smaller than that set for
  -      <code>maxProcessors</code>.  The default value is 5.</p>
  +      when this <strong>Connector</strong> is first started.  The connector
  +      will also make sure it has the specified number of idle processing
  +      threads available. This attribute should be set to a value smaller 
  +      than that set for <code>maxThreads</code>.  The default value is 4.</p>
       </attribute>
   
       <attribute name="port" required="true">
  @@ -185,6 +194,11 @@
         will create a server socket and await incoming connections.  Your
         operating system will allow only one server application to listen
         to a particular port number on a particular IP address.</p>
  +    </attribute>
  +
  +    <attribute name="protocol" required="false">
  +      <p>This attribute value must be <code>HTTP/1.1</code> to use the HTTP
  +      handler, which is the default.</p>
       </attribute>
   
       <attribute name="proxyName" required="false">
  
  
  
  1.6       +6 -39     jakarta-tomcat-catalina/webapps/docs/config/jk2.xml
  
  Index: jk2.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-tomcat-catalina/webapps/docs/config/jk2.xml,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- jk2.xml	28 Jan 2003 18:24:42 -0000	1.5
  +++ jk2.xml	29 Jul 2003 16:40:36 -0000	1.6
  @@ -22,12 +22,7 @@
     where you wish to invisibly integrate Tomcat 5 into an existing (or new)
     Apache installation, and you want Apache to handle the static content
     contained in the web application, and/or utilize Apache's SSL
  -  processing.  In many application environments, this will result in
  -  better overall performance than running your applications under
  -  Tomcat stand-alone using the <a href="http11.html">HTTP/1.1 Connector</a>.  
  -  However, the only way to know for sure whether it will provide better 
  -  performance for <strong>your</strong> application is to try it both 
  -  ways.</p>
  +  processing.</p>
   
     <p>This connector supports load balancing when used in conjunction with
     the <code>jvmRoute</code> attribute of the 
  @@ -45,12 +40,6 @@
   
     <attributes>
   
  -    <attribute name="className" required="true">
  -      <p>Java class name of the implementation to use.  This class must
  -      implement the <code>org.apache.catalina.Connector</code> interface.
  -      You must specify the standard value defined below.</p>
  -    </attribute>
  -
       <attribute name="enableLookups" required="false">
         <p>Set to <code>true</code> if you want calls to
         <code>request.getRemoteHost()</code> to perform DNS lookups in
  @@ -89,8 +78,8 @@
     <subsection name="Standard Implementation">
   
     <p>The standard implementation of <strong>JK 2 Connector</strong> is
  -  <strong>org.apache.coyote.tomcat4.CoyoteConnector</strong>, but you
  -  must specify the protocolHandlerClassName attribute (see below).</p>
  +  <strong>org.apache.coyote.tomcat5.CoyoteConnector</strong>, but you
  +  must specify the protocol attribute (see below).</p>
   
     <p><strong>This implementation supports the AJP 1.3 protocol.</strong></p>
   
  @@ -99,36 +88,14 @@
   
     <attributes>
   
  -    <attribute name="acceptCount" required="false">
  -      <p>The maximum queue length for incoming connection requests when
  -      all possible request processing threads are in use.  Any requests
  -      received when the queue is full will be refused.  The default
  -      value is 10.</p>
  -    </attribute>
  -
       <attribute name="debug" required="false">
         <p>The debugging detail level of log messages generated by this
         component, with higher numbers creating more detailed output.
         If not specified, this attribute is set to zero (0).</p>
       </attribute>
   
  -    <attribute name="maxProcessors" required="false">
  -      <p>The maximum number of request processing threads to be created
  -      by this <strong>Connector</strong>, which therefore determines the
  -      maximum number of simultaneous requests that can be handled.  If
  -      not specified, this attribute is set to 20.</p>
  -    </attribute>
  -
  -    <attribute name="minProcessors" required="false">
  -      <p>The number of request processing threads that will be created
  -      when this <strong>Connector</strong> is first started.  This
  -      attribute should be set to a value smaller than that set for
  -      <code>maxProcessors</code>.  The default value is 5.</p>
  -    </attribute>
  -
  -    <attribute name="protocolHandlerClassName" required="false">
  -      <p>This attribute value must be 
  -      <code>org.apache.jk.server.JkCoyoteHandler</code> to use the JK 2
  +    <attribute name="protocol" required="true">
  +      <p>This attribute value must be <code>AJP/1.3</code> to use the JK 2
         handler.</p>
       </attribute>
   
  @@ -148,7 +115,7 @@
   
   <section name="Configuration HOWTOs">
   
  -  <p>Please refer to the <a href="../coyote/jk2/index.html">Coyote JK 2 documentation</a> 
  +  <p>Please refer to the <a href="http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk2/doc/">JK documentation</a> 
        for HOWTOs and complete configuration information.</p>
   
   </section>
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org