Also look at the memory useage of your servlet code, jsps, etc., ...
Take a look at the objects you create and see if they are being
dereferenced as you'd expect. Tomcat recycles certain instance objects
(like servlets) instead of creating/destroying them per requests for
performance reasons. The side effect is that any objects they reference
will also be held over for the next request unless you purposely clean
them up.
--David
John McClain wrote:
I am trying to find a memory leak in our web application.
I have set JProfiler up to take a heap snapshot upon every entry and exit of
a screen in our web application; This is because upon entry of a screen, we
write data to the user session, and upon exit we remove data from the user
session. The only time we store or remove data is to a user session - other
than an initial lifecycle listener load of application context which remains
static. JProfiler consistently shows that overall, memory usage has a net
increasing trend, yet when I analyze our user sessions over time, the
sessions do not increase in net memory usage. What is the best strategy to
find this memory leak??? If it is not in user session memory, then can I
assume it is a Tomcat memory leak???
John McClain
Senior Software Engineer
TCS Healthcare
[EMAIL PROTECTED]
(530)886-1700x235
Skepticism is the first step toward truth
-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
