You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-user@portals.apache.org by nostah <no...@wp.pl> on 2002/03/07 18:44:44 UTC
jetspeed does not free allocated memory on tomcat v4+
hello everyone,
During my experiments with jetspeed 1.3a2 (and also with version from CVS) I
have encountered a problem:
all the java processes launched by tomcat persist after its shutdown.
I'm not sure if this is jetspeed or tomcat bug, but it happens everytime I
start and stop tomcat v4.0.1 or 4.0.2 while 3.3a works fine.
I have posted a bug report to bugzilla and you can see the little discussion
there ( http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6839 ). I've tried
to turn the feeding threads off and no open connection persists after tomcat
shutdown. Also some of the java processes die after few seconds but rest of
it stays. I can see "Turbine: Done shutting down!" message in jetspeed.log,
but no error can be found there. Is anyone on the list experiencing similar
problem?
regards,
Bartek.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: jetspeed does not free allocated memory on tomcat v4+
Posted by Mark McGettrick <mg...@chromavoid.com>.
[ nostah ]
> hello everyone,
> During my experiments with jetspeed 1.3a2 (and also with version from CVS) I
> have encountered a problem:
> all the java processes launched by tomcat persist after its shutdown.
> I'm not sure if this is jetspeed or tomcat bug, but it happens everytime I
> start and stop tomcat v4.0.1 or 4.0.2 while 3.3a works fine.
> I have posted a bug report to bugzilla and you can see the little discussion
> there ( http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6839 ). I've tried
> to turn the feeding threads off and no open connection persists after tomcat
> shutdown. Also some of the java processes die after few seconds but rest of
> it stays. I can see "Turbine: Done shutting down!" message in jetspeed.log,
> but no error can be found there. Is anyone on the list experiencing similar
> problem?
yes, i have the same exact problem, and would also be interested in
the solution, if any...
-mark
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>