hing there :( and there is enough free space.
There is also
-XX:HeapDumpPath=DIRECTORY_OR_FILE
(Caution: I don't know, if all JVM versions that implement
-XX:+HeapDumpOnOutOfMemoryError, implement this one too).
You should check in the process table (if it's a unix like system) if
your
free space.
>
>
> > There is also
> >
> > -XX:HeapDumpPath=DIRECTORY_OR_FILE
> >
> > (Caution: I don't know, if all JVM versions that implement
> > -XX:+HeapDumpOnOutOfMemoryError, implement this one too).
> >
> > You should check in the process table (
; -XX:HeapDumpPath=DIRECTORY_OR_FILE
>
> (Caution: I don't know, if all JVM versions that implement
> -XX:+HeapDumpOnOutOfMemoryError, implement this one too).
>
> You should check in the process table (if it's a unix like system) if
> your switches are picked up appropriat
In the working directory of the process. Of course you need enough free
disk space.
There is also
-XX:HeapDumpPath=DIRECTORY_OR_FILE
(Caution: I don't know, if all JVM versions that implement
-XX:+HeapDumpOnOutOfMemoryError, implement this one too).
You should check in the process tabl
I specified that parameter in JAVA_OPTS variable, but after the first
"java.lang.OutOfMemoryError: Java heap space" error, no dump file was created.
Where should that file be created by default? any clue?
Thanks
--
Leggi GRATIS le tue mail con