3 Replies Latest reply on Apr 22, 2017 6:42 PM by Helen Chen

    Wildfly crash when gc rotate log

    Helen Chen Novice

      Hi there,

       

      I had a situation that I suspect Wildfly crash is related to GC log rotating.

       

      I'm using solaris 10, java 1.8, Wildfly 10.0.Final. And I set the GC options to be the following:

      JAVA_OPTS="$JAVA_OPTS -XX:-HeapDumpOnOutOfMemoryError -verbosegc -XX:+PrintGCDetails -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=30 -XX:GCLogFileSize=30M -XX:+PrintGCDateStamps -XX:-TraceClassUnloading -Xloggc:/mylocation/standalone/log/gc.log"

       

      for some reason, one day I saw the last line of gc log is like:

      2017-03-01 10:47:58 GC log file has reached the maximum size. Saved as /mylocation/standalone/log/gc.log.0

       

      and the gc.log.1 file seems created, but size is 0. the Wildfly server log also stopped at this timestamp. from server.log file, everything was running normal, no error, it is just suddenly ended at this timestamp when gc rotate file.  I couldn't tell if java process was running at that time because it was not recorded, but I felt the java process may just suddenly dead, otherwise the server.log file should not just suddenly ended.

       

      Wildfly has been running well for sometime, but I never paid attention if the gc log file ever rotated, so I cannot tell if this is the first time it got rotated.

       

      I never saw this situation before. Does anyone know any issues related to java 1.8, gc log rotating?

       

      Any suggestions are greatly appreciate.

       

      Thanks, Helen