imagine, is to make sure the dummy JSP is always present.
Chris Walker
-Original Message-
From: Sai Sivanesan [mailto:[EMAIL PROTECTED]
Sent: 07 September 2003 02:06
To: Tomcat Users List
Subject: Re: PROBLEMS: memory / cpu usage - Tomcat 3.2.1 - SOLVED!
ok. i have found my elusive problem
I don't think this is a known issue - i havn't found any refernce to it any
hwere this was on tomcat version 3.2.1 mod_jk version is unknow as i stupidly
pulled it the other day.
Sai.
On Sun, 7 Sep 2003 12:50:18 +0400, Anton Tagunov wrote
Hello, All!
SS once the 404 is logged, the
I have setup a test box on our internal network with jmeter to generate some
load - will monitor it over the next few days and post my results. Stay Tuned.
Sai.
On Mon, 8 Sep 2003 09:23:30 +0100 , Walker Chris wrote
Now that's interesting. I've been following this thread because
I've just
Anton I found the versions in another thread i had posted
RedHat 7.2
Apache 1.3.20
Tomcat 3.2.1
mod_jk.so mod_jk.so-ap1.3.27-eapi-rh72
Sai.
On Mon, 8 Sep 2003 16:24:46 -0400, Sai Sivanesan wrote
I don't think this is a known issue - i havn't found any refernce to
it any hwere this
Hello, All!
SS once the 404 is logged, the apache - tomcat connection does not
SS terminate. it stays running, and starts to consume cpu time
Is this a known issue?
What connector + Tomcat versions are vulnerable?
Anton
-
ok. i have found my elusive problem. our client has a site with fairly
moderate usage. and over the years we have changes the site a fair bit. it
seems that the problem stems from requesting a jsp file that is no longer on
the server - once the 404 is logged, the apache - tomcat connection
We have a box[P3/700/512MBram] serving JSPs, with about 20 virtual hosts - and
the server comes to a grinding halt after about 12-18 hours. The server gets
about 30K hits per week, so it not exactly overloaded...
versions:
RedHat 7.2
Apache 1.3.20
Tomcat 3.2.1
mod_jk.so
