Hi,

I have now managed to do some analysis of the classes that are
referencing the leaked objects, can anyone help me interpret these
results?

I got jmap/jhat working by upgrading to JRE 1.6.0_05, and took a heap
dump at a time after a period of stress when all SOAP/XML connections
had been closed (so no requests were outstanding).  I had also forced
full garbage collection a few times.  There were many
org.apache.tomcat.util.buf.MessageBytes objects still referenced, which
all seem to be held directly and indirectly by org.apache.coyote.Request
objects.  These are referenced by several classes, which is where I get
a bit lost:

[EMAIL PROTECTED] (70 bytes) :
field request
[EMAIL PROTECTED] (120 bytes) : field
request
[EMAIL PROTECTED] (153 bytes) : field
coyoteRequest
[EMAIL PROTECTED] (68 bytes) : field req
[EMAIL PROTECTED] (78 bytes) : field
coyoteRequest
[EMAIL PROTECTED] (78 bytes) : field req

Where do I go next to find out who is keeping these Request objects
alive?

Thanks,
Tom.

---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to