I'm not certain if setting keep-alive will speed things up, but since you have a firewall you should probably use it.
>From the documentation: socket_keepalive False This directive should be used when you have a firewall between your webserver and the Tomcat engine, who tend to drop inactive connections. This flag will told Operating System to send KEEP_ALIVE message on inactive connections (interval depend on global OS settings, generally 120ms), and thus prevent the firewall to cut the connection. To enable keepalive set this property value to the number greater then 0. The problem with Firewall cutting inactive connections is that sometimes, neither webserver or tomcat have information about the cut and couldn't handle it. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 24, 2005 12:12 PM To: Tomcat Users List Subject: Re: isapi_redirect performance issues I did the packet trace and here is some more information: There are more packets with IIS as compared to Apache – with IIS the response body is in a separate packet than the packet containing the Status Code 200 and also I see "HTTP/1.1 100 Continue" messages sent by server to the client. In Apache the response body is in the same packed at the Status Code 200 packet and there are no "HTTP/1.1 100 Continue" packets. Any help/suggestions/ideas would be appreciated. Thanks Ahmed ----- Original Message ----- From: [EMAIL PROTECTED] Date: Monday, May 23, 2005 3:19 pm Subject: isapi_redirect performance issues > We are using Tomcat 5.5.9 with IIS on the front end. IIS is serving > all the static content and forwards the servlet requests to Tomcat > using the latest version of isapi_redirect.dll and ajp13 protocol. > After deploying the aplication over a server and accessing it through > the internet I am noticing 8x to 10x performance slowdown when > connecting to the application via port 80 as opposed to the direct > port 8080. > I > tried using Apache WebServer in front instead of IIS and that works > great – the performance problem is ONLY when using IIS in the front. > > Unfortunately my application has to be deployed with IIS and only port > 80 open in the firewall. I have been able to reproduce this problem by > generating a small 250 characters html page in response to the GET > request. With Apache or connecting to Tomcat directly it takes about > 20ms for the test client to get the page. Connecting through IIS it > takes about 173ms. Has anybody been successfully using the IIS/Tomcat > integration over the internet? Is there anything that can be done to > improve the performance? IIS is also serving the static pages with > good performance so its not a problem with standalone IIS either. > Any > idea/suggestions? > > Thanks > Ahmed > > > ------------------------------------------------------------------- > -- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
