httpd & jk2 connections persisting in CLOSE_WAIT state

Sam Seaver Mon, 17 May 2004 14:09:55 -0700

Dear all,

Im running

Httpd 2.0.48
Tomcat 4.1.24

Connect by JK2 (unfortunately, I have no record of the version number)

on RH9

This set-up has worked really well, up till recently, where I found that after a couple of visits to the JSP pages compiled by my tomcat server caused a couple of CLOSE_WAIT connections to persist:

tcp 1 0 127.0.0.1:42567 127.0.0.1:8009 CLOSE_WAIT

The JK2 connector is running at port 8009, and this is the connection between a spawned httpd process and the JK2 connector, or so I believe.

I recently did a massive cut down on my server.xml file, (backing it up of course) to all the essentials I thought I needed and nothing more. So I'm posting it below:

<Server port="8005" shutdown="SHUTDOWN" debug="0"> <Service name="Monster">  <Connector className="org.apache.coyote.tomcat4.CoyoteConnector" port="8009" minProcessors="5" maxProcessors="75" enableLookups="true" redirectPort="8443" acceptCount="10" debug="99" scheme="http" connectionTimeout="6000" useURIValidationHack="false" protocolHandlerClassName="org.apache.jk.server.JkCoyoteHandler"/>

   <!-- Define the top level container in our container hierarchy -->
   <Engine name="Standalone" defaultHost="localhost" debug="0">
     <Valve className="org.apache.catalina.valves.RequestDumperValve"/>

     <!-- Global logger unless overridden at lower levels -->
     <Logger className="org.apache.catalina.logger.FileLogger"
             prefix="catalina_log." suffix=".txt"
             timestamp="true" verbosity="4"/>

<Host name="monster.northwestern.edu" debug="99" appBase="/home/monster/web" unpackWARs="false" autoDeploy="false">

           <Context path="" docBase="" debug="99" reloadable="false"/>

<Valve className="org.apache.catalina.valves.AccessLogValve" directory="logs" prefix="monster_access_log." suffix=".txt" pattern="common" resolveHosts="false"/> </Host> </Engine> </Service> </Server>

my website is not going to be used a lot, maybe more in July, but I really need to make sure I can keep it running for months on end, and there's no way its doing that, it keeps getting 'blocked' by these CLOSE_WAITs im getting, any insight?

By the way, when I shut down Catalina, the CLOSE_WAITs persist, but they go away if I restart httpd.

Cheers
Sam


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

httpd & jk2 connections persisting in CLOSE_WAIT state

Reply via email to