2

can anyone explain about this error message? we are using IBM jre to run java application Its occupying more space on the server.

JVMDUMP006I Processing dump event "systhrow", detail "java/lang/OutOfMemoryError" - please wait.
JVMDUMP006I Processing dump event "systhrow", detail "java/lang/OutOfMemoryError" - please wait.
JVMDUMP032I JVM requested Heap dump using '/home/sathish/jetty6/heapdump.20110417.114115.18926.0001.phd' in response to an event
JVMDUMP010I Heap dump written to /home/sathish/jetty6/heapdump.20110417.114115.18926.0001.phd
JVMDUMP032I JVM requested Heap dump using '/home/sathish/jetty6/heapdump.20110417.114115.18926.0002.phd' in response to an event
JVMDUMP010I Heap dump written to /home/sathish/jetty6/heapdump.20110417.114115.18926.0002.phd
JVMDUMP032I JVM requested Heap dump using '/home/sathish/jetty6/heapdump.20110417.114115.18926.0003.phd' in response to an event
JVMDUMP010I Heap dump written to /home/sathish/jetty6/heapdump.20110417.114115.18926.0003.phd
JVMDUMP032I JVM requested Java dump using '/home/sathish/jetty6/javacore.20110417.114115.18926.0004.txt' in response to an event
JVMDUMP010I Java dump written to /home/sathish/jetty6/javacore.20110417.114115.18926.0004.txt
Improve this question
4
  • 5
    Give it more memory?
    – Ignacio Vazquez-Abrams
    Apr 18, 2011 at 5:04
  • Thanks. we have given the heap size memory -Xms3000M -Xmx3000M, is that ok or do we need increase the memory? our RAM size is 7.6 GB.
    – sathishkumar
    Apr 18, 2011 at 5:21
  • Could indicate a memory leak (i.e. a bug in the application that causes it to keep memory/objects around that should not be kept).
    – Robin Green
    Apr 18, 2011 at 7:31
  • You can increase the memory on the instance, I have a Jboss server running at -Xms2000M -Xmx6500M. I opt for the lower -Xms because spawned processes will take that as their initial memory footprint. It will cause issues if it is too high and you spawn sub processes.
    – Flashman
    Apr 18, 2011 at 14:37

1 Answer 1

Reset to default
1

I think you should enable JMX port on your JVM and run the Mission Control product to monitor the memory as your JVM runs. Using Mission Control, you should be able to see what the problem is.

Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.