4 Replies Latest reply on May 23, 2016 9:05 AM by Route nl

    HeapDumpOnOutOfMemoryError JVM option doesn't seem to work for Wildfly process

    Route nl Newbie

      We currently have an OutOfMemoryError problem with our deployment which we need to investigate. When the problem occurs, we get the OutOfMemoryError in the console.log (not in the server.log), with more information available in the noted hs_err_pidxxx.log.

       

      Now, we want to examine the memory on the point that it crashes, so we added the

      -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/heapdump/oom.hprof
      
      

      parameters to our JVM settings.

       

      However, it seems the command doesn't work. When the error occurs now (on the expected timeframe), instead of the OutOfMemoryError & hs_err_pidxxx.log, we get a

      [0m*** JBossAS process (3773) received KILL signal ***
      
      

      in the console.log and it didn't make a heapdump.

       

      Do we have wrong parameters in our JVM options? Or is this a known issue with our current wildfly installation?

       

      We use Wildfly 8.2.0.Final. Our current JVM options are:

      java -D[Standalone] -server -Xms12500m -Xmx20g -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/heapdump/oom.hprof -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Dorg.jboss.boot.log.file=/opt/wildfly/standalone/log/server.log -Dlogging.configuration=file:/opt/wildfly/standalone/configuration/logging.properties -jar /opt/wildfly/jboss-modules.jar -mp /opt/wildfly/modules org.jboss.as.standalone -Djboss.home.dir=/opt/wildfly -Djboss.server.base.dir=/opt/wildfly/standalone -c standalone.xml
      
      

       

      Java version:

      java version "1.8.0_74"
      Java(TM) SE Runtime Environment (build 1.8.0_74-b02)
      Java HotSpot(TM) 64-Bit Server VM (build 25.74-b02, mixed mode)