tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 35497] - tomcat5 stops responding to requests, leaves zombie processes, no response to TERM signal
Date Fri, 15 Jul 2005 10:15:57 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=35497>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=35497


kaichun.lin@gmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|major                       |normal
             Status|RESOLVED                    |REOPENED
          Component|Unknown                     |Servlet & JSP API
         OS/Version|Linux                       |Windows 2000
           Platform|Other                       |PC
         Resolution|INVALID                     |
            Version|5.5.9                       |5.0.28




------- Additional Comments From kaichun.lin@gmail.com  2005-07-15 12:15 -------
Hello, I appeared to have the exact same problem but it happened on Windows.

Server 1:
Windows 2000
5.00.2195
Service Pack 4
Single Processor (Athlon XP 2000+)
Tomcat 5.0.28
J2SDK1.4.2_03


Server 2:
Original dev/test server:
Windows 2000
5.00.2195
Service Pack 4
1/2/4 Xeon CPUs @ 2.4GHz (removing CPUs didn't help the situation)
Tomcat 5.0.28
J2SDK1.4.2_08


Server 1 listed above worked without any problems. However, when I deployed the
service on server 2, Tomcat would stop responding after the servlets are not
accessed for a period of time (around 4-5 hrs). Executing shutup.bat produced no
visible effect. Strangely, as far as I can tell, the JSP pages worked just fine. 
When I modified the web.xml file within the WEB-INF directory of my application,
the supposely dead Tomcat did a context-reload and the previously unresponding
servlets came back alive too. After some futher testings, to my amazement, I
found that could bring Tomcat back alive by simply focus on the Tomcat console
and pressed "Enter" (I assum press any other key would work too).

I would appreaciate it if anyone can shed some light on this matter, and for now
I'll test to see whether or not having a external thread calling a dummy servlet
periodicaly can remove this problem.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org


Mime
View raw message