1 Reply Latest reply on Jul 7, 2011 11:00 AM by 873955

    fatal error in JVM

      My application is a webgame server side. We developed it with apache-MINA 2.0 and deployed the app in Tomcat6.0.18.

      The OS is CentOS release 4.8 (Final)
      java version "1.6.0_18"
      Java(TM) SE Runtime Environment (build 1.6.0_18-b07)
      Java HotSpot(TM) 64-Bit Server VM (build 16.0-b13, mixed mode)

      The following is a part of the jvm crash log (how can I paste the whole log?)
      # A fatal error has been detected by the Java Runtime Environment:
      #  SIGSEGV (0xb) at pc=0x0000002a95c9463c, pid=4930, tid=1080228192
      # JRE version: 6.0_18-b07
      # Java VM: Java HotSpot(TM) 64-Bit Server VM (16.0-b13 mixed mode linux-amd64 )
      # Problematic frame:
      # V  [libjvm.so+0x62263c]
      # If you would like to submit a bug report, please visit:
      #   http://java.sun.com/webapps/bugreport/crash.jsp
      ---------------  T H R E A D  ---------------
      Current thread (0x0000002b6a231800):  GCTaskThread [stack: 0x000000004052f000,0x0000000040630000] [id=4935]
      ---------------  P R O C E S S  ---------------
      Java Threads: ( => current thread )
        0x0000002b6db18800 JavaThread "NioProcessor-2151" [_thread_in_native, id=10983, stack(0x000000004406a000,0x000000004416b000)]
        0x0000002b72b72000 JavaThread "pool-865-thread-2" [_thread_blocked, id=10982, stack(0x000000004416b000,0x000000004426c000)]
        0x0000002b71bc6000 JavaThread "NioSocketConnector-432-idleStatusChecker" [_thread_blocked, id=10981, stack(0x0000000043c66000,0x0000000043d67000)]
        0x0000002b6e217000 JavaThread "pool-862-thread-1" [_thread_blocked, id=10955, stack(0x0000000044771000,0x0000000044872000)]
        0x0000002b72b71800 JavaThread "NioSocketConnector-431-idleStatusChecker" [_thread_blocked, id=10953, stack(0x0000000043963000,0x0000000043a64000)]
        0x0000002b710eb800 JavaThread "pool-3-thread-224" [_thread_blocked, id=10941, stack(0x0000000043f69000,0x000000004406a000)]
      Other Threads:
        0x0000002b6a2ce800 VMThread [stack: 0x0000000040630000,0x0000000040731000] [id=4936]
        0x0000002b6a305800 WatcherThread [stack: 0x0000000040d37000,0x0000000040e38000] [id=4943]
      =>0x0000002b6a231800 (exited) GCTaskThread [stack: 0x000000004052f000,0x0000000040630000] [id=4935]
      VM state:at safepoint (normal execution)
      VM Mutex/Monitor currently owned by a thread:  ([mutex/lock_event])
      [0x0000000040110700] Threads_lock - owner thread: 0x0000002b6a2ce800
      [0x0000000040110c00] Heap_lock - owner thread: 0x0000002b6e79e800
       PSYoungGen      total 343424K, used 343424K [0x0000002b29730000, 0x0000002b3ec80000, 0x0000002b69730000)
        eden space 339264K, 100% used [0x0000002b29730000,0x0000002b3e280000,0x0000002b3e280000)
        from space 4160K, 100% used [0x0000002b3e870000,0x0000002b3ec80000,0x0000002b3ec80000)
        to   space 5120K, 8% used [0x0000002b3e280000,0x0000002b3e2f0000,0x0000002b3e780000)
       PSOldGen        total 699072K, used 652147K [0x0000002aa9730000, 0x0000002ad41e0000, 0x0000002b29730000)
        object space 699072K, 93% used [0x0000002aa9730000,0x0000002ad140ccb8,0x0000002ad41e0000)
       PSPermGen       total 131072K, used 43628K [0x0000002a99730000, 0x0000002aa1730000, 0x0000002aa9730000)
        object space 131072K, 33% used [0x0000002a99730000,0x0000002a9c1cb298,0x0000002aa1730000)
      VM Arguments:
      jvm_args: -Xms1024m -Xmx3072m -XX:PermSize=128M -XX:MaxPermSize=256m -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.util.logging.config.file=/usr/local/tomcat6/conf/logging.properties -Djava.endorsed.dirs=/usr/local/tomcat6/endorsed -Dcatalina.base=/usr/local/tomcat6 -Dcatalina.home=/usr/local/tomcat6 -Djava.io.tmpdir=/usr/local/tomcat6/temp 
      java_command: org.apache.catalina.startup.Bootstrap start
      Launcher Type: SUN_STANDARD
      Environment Variables:
      Signal Handlers:
      SIGSEGV: [libjvm.so+0x70f1a0], sa_mask[0]=0x7ffbfeff, sa_flags=0x10000004
      SIGBUS: [libjvm.so+0x70f1a0], sa_mask[0]=0x7ffbfeff, sa_flags=0x10000004
      SIGFPE: [libjvm.so+0x5d7f70], sa_mask[0]=0x7ffbfeff, sa_flags=0x10000004
      SIGPIPE: [libjvm.so+0x5d7f70], sa_mask[0]=0x7ffbfeff, sa_flags=0x10000004
      SIGXFSZ: [libjvm.so+0x5d7f70], sa_mask[0]=0x7ffbfeff, sa_flags=0x10000004
      SIGILL: [libjvm.so+0x5d7f70], sa_mask[0]=0x7ffbfeff, sa_flags=0x10000004
      SIGUSR1: SIG_DFL, sa_mask[0]=0x00000000, sa_flags=0x00000000
      SIGUSR2: [libjvm.so+0x5da790], sa_mask[0]=0x00000000, sa_flags=0x10000004
      SIGHUP: [libjvm.so+0x5da4e0], sa_mask[0]=0x7ffbfeff, sa_flags=0x10000004
      SIGINT: SIG_IGN, sa_mask[0]=0x00000000, sa_flags=0x00000000
      SIGTERM: [libjvm.so+0x5da4e0], sa_mask[0]=0x7ffbfeff, sa_flags=0x10000004
      SIGQUIT: [libjvm.so+0x5da4e0], sa_mask[0]=0x7ffbfeff, sa_flags=0x10000004
      ---------------  S Y S T E M  ---------------
      OS:CentOS release 4.8 (Final)
      uname:Linux 2.6.9-89.ELsmp #1 SMP Mon Jun 22 12:31:33 EDT 2009 x86_64
      libc:glibc 2.3.4 NPTL 2.3.4 
      rlimit: STACK 10240k, CORE 0k, NPROC 71680, NOFILE 600000, AS infinity
      load average:0.00 0.02 0.00
      CPU:total 4 (8 cores per cpu, 2 threads per core) family 6 model 26 stepping 5, cmov, cx8, fxsr, mmx, sse, sse2, sse3, ssse3, sse4.1, sse4.2, popcnt, ht
      Memory: 4k page, physical 8168728k(6755220k free), swap 8369824k(8369824k free)
      vm_info: Java HotSpot(TM) 64-Bit Server VM (16.0-b13) for linux-amd64 JRE (1.6.0_18-b07), built on Dec 17 2009 13:42:22 by "java_re" with gcc 3.2.2 (SuSE Linux)
      time: Thu Jul 15 23:50:46 2010
      elapsed time: 43595 seconds
      Following the crash log, I think the JVM crashed in GC.
      Does anybody know how to solve it? what did it caused?

      Sorry for my poor English. :)
        • 1. Re: fatal error in JVM
          I faced the same error with a different application in my tomcat container.
          After modifying the garbage collection options (I read an issue in a different blog) and 9 nine days without any problems
          the application crashes again.

          Did you find a solution?