----------------------------------------------------------------
BEFORE YOU POST, search the faq at <http://java.apache.org/faq/>
WHEN YOU POST, include all relevant version numbers, log files,
and configuration files. Don't make us guess your problem!!!
----------------------------------------------------------------
Has anyone else experienced a problem where the number of threads
just keeps increasing, until the JVM runs out of slots and then
restarts?
It seems to be related to these entries in mod_jserv.log:
[27/02/2000 12:24:50:629] (EMERGENCY) ajp12[1]: cannot scan servlet
headers (500)
[27/02/2000 12:24:50:642] (ERROR) an error returned handling request
via protocol "ajpv12"
The weird part is that all our servlets set their thread's name, and
these threads have no name but the default one. So I'm wondering if
these are GC threads, or if Jserv just isn't cleaning the
threads/instances up in this error case.
These are SingleThreadModel servlets.
Any insight would be welcome. Jserv has plenty of memory allocated
and there are no other apparent problems.
It would be cool if Jserv would set the thread name to the name of the servlet.
Apache/1.3.9 (Unix) ApacheJServ/1.1
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
