Hi Miguel,
To be more precise about used memory and active threads count, I think
that you could send a screenshot of the main graphics of javamelody in
your browser (used memory, http sessions, active threads, etc...).
And once you have the heap dump as said by Christopher, "Eclipse MAT" is
quite good to analyze the heap dump.
Emeric
Le 03/05/2012 16:52, Christopher Schultz a écrit :
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Miguel,
On 5/3/12 6:35 AM, Miguel González Castaños wrote:
Anything I can check or any setting I can set to get more
information in the next crash?
Add "-XX:+HeapDumpOnOutOfMemoryError" to your CATALINA_OPTS
environment variable before you launch Tomcat and you'll get a heap
dump file when OOME occurs. You could also enable verbose gc if you
want to go back and graph the memory usage.. but if you're using
javamelody you probably already have that.
Once you have the heap dump, look for either single objects that are
taking a huge amount of memory or one particular class that has a lot
of objects and/or takes up a lot of memory per object. Follow those
objects to their GC roots and you'll find out where the references
are. Perhaps you have a memory leak entirely by accident, or maybe a
cache that isn't tuned properly for your heap size.
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk+im5MACgkQ9CaO5/Lv0PD7uQCgiKEtK56xU+l6kw/0UmxruLBf
95MAnRJ3hfZd/POoD09B12MglevNqekk
=tzaU
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
