https://issues.apache.org/bugzilla/show_bug.cgi?id=49395
--- Comment #4 from sylvain.laur...@gmail.com 2010-06-07 17:25:05 EDT --- Konstantin, your use cases are what I had in mind. Most notably, it's interesting to know whether the leaking context is the first one that was deployed or subsequent ones. In the former case, this might indicate that some Thread is spawned once per JVM with an incorrect CCL (the kind of leak the JreMemoryLeakPreventListener tries to avoid). I know that it does not replace a full heap analysis with a tool, but it gives a quick clue. I'll take your points into account and post a new patch in a couple of days. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- 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
