https://issues.apache.org/bugzilla/show_bug.cgi?id=56472
Mark Thomas <ma...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |INVALID
--- Comment #7 from Mark Thomas <ma...@apache.org> ---
All the indications are that the root cause of this issue lies in application
code or third party library code rather than Tomcat code. I am therefore
resolving this as invalid. The users list is the best place to get help with
this issue.
One pointer that may help you move this a little further forward before you
post to the users list is that I have seen cases where the JVM fails to
correctly report all GC roots. Tracking down the memory leak in these cases is
a complete pain. I hit a similar issue with a Spring app and had to build the
relevant Spring libraries locally so I could do what was effectively a binary
search to track down the line of code that triggered the issue. It turned out
to be a memory leak somewhere in the JRE's XML parser but I never could track
down exactly what as the JVM never reported the GC root.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
