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=20268>. 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=20268 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[EMAIL PROTECTED] Status|RESOLVED |REOPENED OS/Version|Windows XP |Windows Server 2003 Resolution|INVALID | ------- Additional Comments From [EMAIL PROTECTED] 2006-01-12 23:20 ------- We also have Tomcat 5.0.28/Java 1.4.2/ColdFusion 6/Windows Server 2003. Sometimes when Tomcat is started, it initializes the installed servlets and the next thing you know, it's pegged the CPU at 100% and memory held by Tomcat (according to the Task Manager) climbs indefinitely until Windows terminates the process. We can reproduce this problem by hammering our most complex servlet **heavily** just as Tomcat is initializing (whether from a boot-up or a restart). If Tomcat is not slammed during initialization, everything is *fine* and Tomcat can operate normally for months at a time. This is a particular problem for us to solve because our business requirements demand up to four full installs a day, and any given one of these installs can cause a Tomcat server to go wild. We would appreciate any help you can offer on 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]