You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Sai Sivanesan <sa...@opensource.dibacanada.com> on 2003/09/07 03:05:34 UTC
Re: PROBLEMS:> memory / cpu usage - Tomcat 3.2.1 - SOLVED!
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 does not
terminate. it stays running, and starts to consume cpu time. a sufficient
number of these will over time, bring the machine to a crawl - to a point
where it is almost impossible to even login via ssh or even locally. Time to
read the conf file to see what we can do about 404 error documents.
Sai.
On Sat, 30 Aug 2003 16:52:21 -0400, Sai Sivanesan wrote
> 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 mod_jk.so-ap1.3.27-eapi-rh72
>
> processes seem to persist longer than they should. here is a line
> out of top: 12568 root 18 0 25300 24M 7924 S 3.8 4.9
> 56:19 java
>
> anyone have similar experiences?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
--
Open WebMail Project (http://openwebmail.org)
Re: 404 leaks (was: PROBLEMS:> memory / cpu usage - Tomcat 3.2.1)
Posted by Sai Sivanesan <sa...@opensource.dibacanada.com>.
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 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 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
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>
> --
> Open WebMail Project (http://openwebmail.org)
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
--
Open WebMail Project (http://openwebmail.org)
Re: 404 leaks (was: PROBLEMS:> memory / cpu usage - Tomcat 3.2.1)
Posted by Sai Sivanesan <sa...@opensource.dibacanada.com>.
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 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
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
--
Open WebMail Project (http://openwebmail.org)
404 leaks (was: PROBLEMS:> memory / cpu usage - Tomcat 3.2.1)
Posted by Anton Tagunov <at...@mail.cnt.ru>.
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