Don't bother with jhat, try eclipse Memory Analysis Tool instead. It's much more friendly and efficient to find leaks.
On 23 nov. 2010, at 12:18, xu cheng wrote: > hi, Chuck.Caldarale > I referenced to these two links > http://blogs.sun.com/fkieviet/entry/classloader_leaks_the_dreaded_java > http://blogs.sun.com/fkieviet/entry/how_to_fix_the_dreaded > and do as the blog tolds, but failed to find the reason of the oom of my > app... > thanks though.. > > by the way, do you have the the jhat the articals mentioned? I went to the > jdk/bin, > but the jhat there seems not work as the author mentioned. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
