Chris,
Are you, per chance, removing the ROOT context? There are known issues if
no root context is defined. I tried duplicating this with non-root contexts
and everything behaved as expected.
-----Original Message-----
From: BugRat Mail System [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 02, 2001 5:25 PM
To: [EMAIL PROTECTED]
Subject: BugRat Report #691 has been filed.
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.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
