HttpConnector[8080] No processor available, rejecting this connection

[arun kamalam]

Hi,

when i run my application on tomcat 4.0 i am getting this type of error. please help me to solve this problem.


2010-06-14 14:17:52 HttpConnector[8080] No processor available, rejecting this connection
2010-06-14 14:17:53 HttpConnector[8080] No processor available, rejecting this connection
2010-06-14 14:17:53 HttpConnector[8080] No processor available, rejecting this connection
2010-06-14 14:17:54 HttpConnector[8080] No processor available, rejecting this connection
2010-06-14 14:17:54 HttpConnector[8080] No processor available, rejecting this connection
2010-06-14 14:17:55 HttpConnector[8080] No processor available, rejecting this connection
2010-06-14 14:17:56 HttpConnector[8080] No processor available, rejecting this connection
2010-06-14 14:18:00 HttpConnector[8080] No processor available, rejecting this connection
2010-06-14 14:18:00 HttpConnector[8080] No processor available, rejecting this connection
2010-06-14 14:18:02 HttpConnector[8080] No processor available, rejecting this connection
2010-06-14 14:18:03 HttpConnector[8080] No processor available, rejecting this connection
2010-06-14 14:18:03 HttpConnector[8080] No processor available, rejecting this connection
2010-06-14 14:18:04 HttpConnector[8080] No processor available, rejecting this connection
2010-06-14 14:18:05 HttpConnector[8080] No processor available, rejecting this connection
2010-06-14 14:18:06 HttpConnector[8080] No processor available, rejecting this connection
2010-06-14 14:20:11 HttpConnector[8080] No processor available, rejecting this connection

my server config is

<Connector className="org.apache.catalina.connector.http.HttpConnector"
port="8080" minProcessors="5" maxProcessors="75"
enableLookups="true" redirectPort="8443"
acceptCount="10" debug="0" connectionTimeout="60000"/>
please help to slove this problem. it is very urgent.

Regards
Arun K

[William Brogden]

Sounds to me like all available connections are in use - possibly with request threads hung up somewhere.

Surely there is more information in the log files.

Whats the last thing that actually worked in this Tomcat installation?

What happens if you restart Tomcat, does it every work?

If this was Tomcat 5 or later I would suggest using the management app to see the status of the request thread pool, but I dont know if you can get it for Tomcat 4.

Bill

[Tim Holloway]

Welcome to the JavaRanch, Arun!

I'm pretty sure that both the management and admin apps were available for Tomcat 4, and in fact, for at least some of the Tomcat 4 versions, they came as part of the base download. Later Tomcat releases required a separate download and install for those webapps.

Please note that Tomcat 4 is about 2 years past its end of life and is no longer supported. Also Tomcat 5 provided significant improvements in performance, so I recommend considering at least Tomcat 5.0, if not 5.5. Best of all would be Tomcat 6, since that's the current active version. For a little longer, at least.