Bug report #691 has just been filed. You can view the report at the following URL: <http://znutar.cortexity.com/BugRatViewer/ShowReport/691> REPORT #691 Details. Project: Tomcat Category: Bug Report SubCategory: New Bug Report Class: swbug State: received Priority: high Severity: critical Confidence: public Environment: Release: 3.2.1 JVM Release: 1.2.2 Operating System: Windows 2000 Pro OS Release: ? Platform: Intel Synopsis: Removing contexts from EmbededTomcat causes cpu util to go to 100% Description: Collection c = m_contexts.values(); for (Iterator x = c.iterator(); x.hasNext();) m_server.removeContext((ServletContext) x.next()); If a request is sent to a "removed" context, the jvm process uses 100% of the cpu, and the process must be killed. The browser does not timeout. Additional requests also hang.Title: BugRat Report # 691
BugRat Report # 691
Project: Tomcat | Release: 3.2.1 |
Category: Bug Report | SubCategory: New Bug Report |
Class: swbug | State: received |
Priority: high | Severity: critical |
Confidence:
public
|
Submitter:
Chris McClelen ( [EMAIL PROTECTED] )
Date Submitted:
Jan 2 2001, 05:24:55 CST
Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )
- Synopsis:
- Removing contexts from EmbededTomcat causes cpu util to go to 100%
- Environment: (jvm, os, osrel, platform)
- 1.2.2, Windows 2000 Pro, ?, Intel
- Additional Environment Description:
- Report Description:
- Collection c = m_contexts.values(); for (Iterator x = c.iterator(); x.hasNext();) m_server.removeContext((ServletContext) x.next()); If a request is sent to a "removed" context, the jvm process uses 100% of the cpu, and the process must be killed. The browser does not timeout. Additional requests also hang.
- Workaround:
- null
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]