Yup that's what I thought was happening. When all threads are busy,
tomcat can't accept any more requests. To an extent tomcat still
accepts some request and waits for a thread to free up but eventually
it'll reject the requests with a 50x error.
Either the tomcat service is legitimately
> From: Etienne Lacombe [mailto:[EMAIL PROTECTED]
> Subject: Tomcat 5.5.20 Stops Responding
>
> I followed your advice and killed the JVM so as to get the
> stack trace when it stopped responding this afternoon.
It's not actually necessary to terminate the process in order to trigger
a thread d
> From: Etienne Lacombe [mailto:[EMAIL PROTECTED]
> Subject: Tomcat 5.5.20 Stops Responding
>
> I was sure my Email had not been sent so that's
> why I resent it.
You can always check the archives to see if your message has made it to
the rest of world:
http://marc.info/?l=tomcat-user
http://ma
> From: Etienne Lacombe [mailto:[EMAIL PROTECTED]
> Subject: Tomcat 5.5.20 Stops Responding
>
> I would like some help in locating the cause of a problem on
> a Tomcat 5.5.20 server.
Any particular reason for reposting the exact same message when David S
already suggested something to try? Why
Regarding the ideas:
1. tomcat 5.5 and java 1.6 should be fine together.
2. If all threads are busy, the AccessLogValve may not show anything.
Something _seems_ to be causing your jdk to turn into a zombie. Sending
a kill signal to the tomcat process so you get a thread dump is probably
best
Hi Etienne,
Etienne Lacombe schrieb:
Hello,
Setup
Linux
Tomcat 5.5.20
Java 1.6
Two ideas:
(1) I am not shure if Tomcat 5.5.20 is compatible with Java 1.6.
(2) Turn on the AccessLogValve in your server.xml config file, so you can see if
the client requests attain your Tomcat. If no
