Tomcat 4.1.24 CoyoteConnector Stops responding

During high volume usage Tomcat's CoyoteConnector stops responding. WHY?

I have a web site that gets about 500,000 page views/day. The current architecture is on Win2K Server Tomcat 4.1.24 + mod_jk 1.2.4 + Apache 1.3.28. During the peak times of the usage the Coyote Connector stops responding, and I cannot find the reason. Driving me mad.
I know that tomcat is not crashing because the process is still alive and it also responds to the calls made thru port 8080 the http connector.
I also know that it is not the database that causes the error, because I have other app servers that can use the database.
I think the problem is not caused by running out of threads since the same problem occurs even when the maxProcessors is set to an absurd number like 9000.
I am sure that the bottleneck is not apache, because even though I open up the connector to accept connections from all IP addresses, when the connector stops responding and apache starts giving 500 errors, I cannot connect to the port 8009. Therefore, I am pretty sure the source of the problem is in the Connectors. WHY?!?!? PLEASE HELP!

The current connector configuration:
   <Connector className="org.apache.coyote.tomcat4.CoyoteConnector"
               address="127.0.0.1" port="8009" minProcessors="50" maxProcessors="1256"
               enableLookups="true" redirectPort="8443"
               acceptCount="300" debug="0" connectionTimeout="20000"
               useURIValidationHack="true"
               protocolHandlerClassName="org.apache.jk.server.JkCoyoteHandler" />

PS: I also tried to have 4 of these connectors running from different ports with modjk loadbalancing, however, they all go down one by one.
laylaylilomAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
vzilkaConnect With a Mentor Commented:
I saw this problem before.
To my understanding it is related to the Apache AJP13 connector, but from the Tomcat side.
It is somehow related to passing a parameter in the HTTP header/cookie that is a defined keyword.
I can't find this in the Tomcat bugbase, but I think it is solved in Tomcat 5.
Is upgrade an option?

Also, try to increase the log level of Tomcat and Apache, to see if you can find any info.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.