portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 6839] - jetspeed does not free allocated memory on tomcat v4+
Date Mon, 04 Mar 2002 13:47:45 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6839>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6839

jetspeed does not free allocated memory on tomcat v4+





------- Additional Comments From noster@venture.org.pl  2002-03-04 13:47 -------
Default tomcat installation (without jetspeed) runs fine and I had no problems
with it at all. Starting and stoping the engine using startup and shutdown
scripts works fine and no processes remain. The problems occur when I deploy
jetspeed.war - all the pages do work but after executing shutdown.sh there are
several java processes that can only be removed with kill command. The problem
exist also when I only start and stop tomcat having jetspeed deployed (without
browsing any page) - some java processes are still existing and they don't wanna
die (which is what I  can personaly understand). 

I haven't found any special error messages in the logs - only exceptions when
I've tried to stop the tomcat twice.

All the machines that I have used for testing have network connection. The
remaining processes could be some pulling threads or so. But what can be the
explanation of the behaviour when no pages were browsed? Do jetspeed starts some
pulling threads at servlet engine initialization time?

I also tried and shutdowned netword interface but the results were identical.

--
To unsubscribe, e-mail:   <mailto:jetspeed-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:jetspeed-dev-help@jakarta.apache.org>


Mime
View raw message