1 Reply Latest reply on May 6, 2006 1:57 AM by spiteri

    Tomcat and Jakarta ISAPI Redirector

      Just a quick one...shoud the connecter settings in the server.xml for the HTTP connecter match the AJP1.3 settings?

      Below is a sample from a production...I am experiencing a high number of server busy requests and sever time outs at the moment.

      Any suggestions?

      <!-- A HTTP/1.1 Connector on port 8080 -->


      <!-- Add this option to the connector to avoid problems with
      .NET clients that don't implement HTTP/1.1 correctly
      restrictedUserAgents="^.*MS Web Services Client Protocol 1.1.4322.*$"
      -->

      <!-- A AJP 1.3 Connector on port 8009 -->

        • 1. Re: Tomcat and Jakarta ISAPI Redirector

          Sorry..the cut and paste didnt work too well...here is the server.xml settings.

          <!-- A HTTP/1.1 Connector on port 8080 -->
           <Connector port="6969" address="xxx.xxx.178.83"
           maxThreads="600" minSpareThreads="100" maxSpareThreads="300"
           strategy="ms" maxHttpHeaderSize="8192"
           emptySessionPath="true"
           enableLookups="false" redirectPort="8443" acceptCount="1000"
           connectionTimeout="120000" disableUploadTimeout="true"/>
          
           <!-- Add this option to the connector to avoid problems with
           .NET clients that don't implement HTTP/1.1 correctly
           restrictedUserAgents="^.*MS Web Services Client Protocol 1.1.4322.*$"
           -->
          
           <!-- A AJP 1.3 Connector on port 8009 -->
           <Connector port="8009" address="xxx.xxx.177.32"
           emptySessionPath="true" enableLookups="false" redirectPort="8443"
           protocol="AJP/1.3"/>