: Tomcat Users List
Objet : Re: RE : memory-leaks in servlets, tool for tracing ?
Laurent,
What about classes with static method and/or static attributes ?
Are they deleted from the old webapp ?
I don't believe that the VM ever releases resources taken up by Class
objects (I think this includes
Howdy,
context-reload occurs. The solution, of course, is not to enable
context-reloading on production :)
This is very good advice.
Yoav Shapira
This e-mail, including any attachments, is a confidential business communication, and
may contain information that is confidential, proprietary
Laurent,
When does a class reload occur ?
I was talking about a context re-load, which dumps everything in the
context and re-starts it in a new ClassLoader.
When u update a JSP ?
Yes, the class gets re-loaded, but not the whole context. This is much
less of a problem.
When u update a class ?
Christopher,
thanks for your comprehensive response !
See more comments down ...
- Original Message -
From: Christopher Schultz [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Sent: Wednesday, October 29, 2003 3:29 PM
Subject: Re: memory-leaks in servlets, tool for tracing
Grisi,
our TC-based webapplication performs well but the java-processes
concerned are showing increasing memory usage over time. For tracing
we already stripped the app down to the very basic to get a clue.
Wasn't successful enough.
Have you looked at the memory over a long time, including
Howdy,
our TC-based webapplication performs well but the java-processes
concerned are showing increasing memory usage over time. For tracing
This basic idea that memory usage should be constant over time is very
common and usually wrong. The JVM will use as much memory as it needs
without
Yoav,
You make a great point about how the app should stabilize it's memory
usage over time. However, I've got a question about memory usage when I
stop (via Tomcat manager) and reload a webapp via a WAR file. If I
understand your point, and I'm close to the max heap size, shouldn't GC
free
Howdy,
You make a great point about how the app should stabilize it's memory
usage over time. However, I've got a question about memory usage when I
stop (via Tomcat manager) and reload a webapp via a WAR file. If I
understand your point, and I'm close to the max heap size, shouldn't GC
free up
What about classes with static method and/or static attributes ?
Are they deleted from the old webapp ?
-Message d'origine-
De : Shapira, Yoav [mailto:[EMAIL PROTECTED]
Envoyé : mercredi 5 novembre 2003 15:57
À : Tomcat Users List
Objet : RE: memory-leaks in servlets, tool for tracing
Objet : RE : memory-leaks in servlets, tool for tracing ?
What about classes with static method and/or static attributes ?
Are they deleted from the old webapp ?
-Message d'origine-
De : Shapira, Yoav [mailto:[EMAIL PROTECTED]
Envoyé : mercredi 5 novembre 2003 15:57
À : Tomcat Users List
-Original Message-
From: Laurent Michenaud [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 05, 2003 10:59 AM
To: Tomcat Users List
Subject: RE : RE : memory-leaks in servlets, tool for tracing ?
It would be good if some of you writes an kind of howTo
that shows :
- a webapp with a memory
Laurent,
What about classes with static method and/or static attributes ?
Are they deleted from the old webapp ?
I don't believe that the VM ever releases resources taken up by Class
objects (I think this includes static resources for a class). There used
to be a VM option, -noclassgc, that was
hi everybody,
our TC-based webapplication performs well but the java-processes concerned are showing
increasing memory usage over time. For tracing we already stripped the app down to the
very basic to get a clue. Wasn't successful enough.
Does anybody's got experience with a profiling toolkit
Howdy,
I like OptimizeIt's heap snapshots.
Yoav Shapira
Millennium ChemInformatics
-Original Message-
From: Dirk Griesbach [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 29, 2003 4:03 AM
To: Tomcat Users List
Subject: memory-leaks in servlets, tool for tracing ?
hi everybody,
our
Grisi,
our TC-based webapplication performs well but the java-processes
concerned are showing increasing memory usage over time. For tracing
we already stripped the app down to the very basic to get a clue.
Wasn't successful enough.
Have you looked at the memory over a long time, including
15 matches
Mail list logo
