On Oct 21, 2005, at 2:53 PM, Jorg Heymans wrote:
1) java.lang.OutOfMemoryError. I can't really say what triggers this,
but it happens every now and then when doing a full build of all
modules.
Any thoughts on how to track down what is happening here?
I've had good luck recently using Java's built-in profiler to
diagnose performance & memory problems. On Java 1.5, you invoke it
like this:
$ java -agentlib:hprof=help
on Java 1.4, there's a stupider syntax
$ java -Xrunhprof:help
I think you can run it on maven with something like this:
$ MAVEN_OPTS="-agentlib:hprof=heap=all" maven
It will dump output on the top allocation sites into a file called
java.hprof.txt, along with a fair amount of information on how to
read it.
--
Scott Lamb <http://www.slamb.org/>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
