Re: Obtaining a memory dump...
Mikhail T. wrote:
Hello!
We know, that sending a Java process signal 3 will cause it to dump the
list of threads to the stderr.
What we would like, however, is the (huge) list of objects.
A vendor's program (we don't have sources) runs for a while here
consuming "modest" 80Mb of memory.
Then -- SOMETHING -- happens, and the process' memory consumption starts
to grow rapidly, until it reaches the maximum heap size (currently set
to 3.2Gb) and reports "OutOfMemoryException".
Are you quite certain? I strongly suspect, but have to ask, isn't it actually
an OutOfMemoryError?
The thing is, with an Error you aren't supposed to let the process live:
An Error is a subclass of Throwable that indicates serious problems that a reasonable application should not try to catch.
(<http://java.sun.com/javase/6/docs/api/java/lang/Error.html>)
and yet,
The process does not die, as the exception is caught (and the memory use returns to normal), but
random things begin to fail and it needs to be restarted...
Explaining, perhaps, why the language Designers told the us not to catch that
Error. Tsk, tsk.
Which would still leave you with the difficulty of diagnosing the problem.
Aside from getting a complete JVM dump, is there anything spitting out in the
error messages that gives any clue?
--
Lew