On Fri, Oct 24, 2003 at 16:01:48 +0200, [EMAIL PROTECTED] wrote: > When everything quiets down, tomcat seems to be unable to service > any http requests. Any attempt to connect to port 10003 with a web > browser eventually causes a "No data in response"-style error message. > At this point it seems the http connector listening on port 10003 has > gone "zombie" on me:
I've figured out what's going wrong. The following exception is printed once on standard out when things fail: java.lang.OutOfMemoryError: unable to create new native thread at java.lang.Thread.start(Native Method) at org.apache.catalina.connector.http.HttpProcessor.threadStart(HttpProcessor.java:1178) at org.apache.catalina.connector.http.HttpProcessor.start(HttpProcessor.java:1262) at org.apache.catalina.connector.http.HttpConnector.newProcessor(HttpConnector.java:937) at org.apache.catalina.connector.http.HttpConnector.createProcessor(HttpConnector.java:868) at org.apache.catalina.connector.http.HttpConnector.run(HttpConnector.java:1075) I looked into the source for HttpProcessor briefly; perhaps the "thread.start()" on line 1178 or the threadStart() call on line 1262 could be surrounded with a try/catch(OutOfMemoryError), and throw a LifecycleException? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]