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:
org.apache.coyote.http11.InternalInputBuffer@0xb1b129a0 (70 bytes) :
field request
org.apache.coyote.http11.Http11Processor@0xb1e30148 (120 bytes) : field
request
org.apache.catalina.connector.Request@0xb2348310 (153 bytes) : field
coyoteRequest
org.apache.coyote.RequestInfo@0xb1b12ad8 (68 bytes) : field req
org.apache.catalina.connector.InputBuffer@0xb2ef90b8 (78 bytes) : field
coyoteRequest
org.apache.coyote.Response@0xb2767d48 (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@...
To unsubscribe, e-mail:
users-unsubscribe@...
For additional commands, e-mail:
users-help@...
