美文网首页
一次jvm崩溃分析

一次jvm崩溃分析

作者: holyABCD | 来源:发表于2018-03-30 10:55 被阅读0次
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007f54769083ee, pid=25523, tid=139999695345408
#
# JRE version: Java(TM) SE Runtime Environment (8.0_45-b14) (build 1.8.0_45-b14)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.45-b02 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# J 9952 C2 com.sss.sss.sss.log.LoggerWrapper.info(Ljava/lang/String;)V (50 bytes) @ 0x00007f54769083ee [0x00007f54769083a0+0x4e]
#
# Core dump written. Default location: /home/xzx/xxx/core or core.25523
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.java.com/bugreport/crash.jsp
#

---------------  T H R E A D  ---------------
Current thread (0x00007f5274019800):  JavaThread "Grizzly-worker(165)" daemon [_thread_in_Java, id=26195, stack(0x00007f54380c1000,0x00007f54381c2000)]

siginfo: si_signo: 11 (SIGSEGV), si_code: 1 (SEGV_MAPERR), si_addr: 0x000000000000000c

Registers:
RAX=0x0000000000000000, RBX=0x00000007844e4f78, RCX=0x0000000000592f67, RDX=0x00000006c54201b0
RSP=0x00007f54381c0210, RBP=0x00000006c12e69f0, RSI=0x00000007844e4e60, RDI=0x00007f54381c0190
R8 =0x00000007844e4e60, R9 =0x00000000d8330ea8, R10=0x0000000000000000, R11=0x00000000d82502e5
R12=0x0000000000000000, R13=0x00000006c1430cc0, R14=0x0000000000000007, R15=0x00007f5274019800
RIP=0x00007f54769083ee, EFLAGS=0x0000000000010282, CSGSFS=0x0000000000000033, ERR=0x0000000000000004
  TRAPNO=0x000000000000000e


Instructions: (pc=0x00007f54769083ee)
0x00007f54769083ce:   c6 44 8b 5e 14 45 85 db 0f 85 71 03 00 00 48 bb
0x00007f54769083de:   98 a9 02 c0 06 00 00 00 44 8b 53 0c 44 8b 5e 10
0x00007f54769083ee:   47 8b 4c d4 0c 45 8b d1 41 83 c2 0a 45 85 d2 0f
0x00007f54769083fe:   8c 24 03 00 00 41 8b c9 83 c1 0b 85 c9 0f 8c 1b

Register to memory mapping:

RAX=0x0000000000000000 is an unknown value
RBX=0x00000007844e4f78 is an oop
java.lang.String
 - klass: 'java/lang/String'
RCX=0x0000000000592f67 is an unknown value
RDX=0x00000006c54201b0 is an oop
java.lang.String
 - klass: 'java/lang/String'
RSP=0x00007f54381c0210 is pointing into the stack for thread: 0x00007f5274019800
RBP=0x00000006c12e69f0 is an oop
com.sss.sss.register.service.impl.ProvisioningServiceImpl
 - klass: 'com/ss/ss/register/service/impl/ProvisioningServiceImpl'
RSI=0x00000007844e4e60 is an oop
com.ss.ss.register.log.LoggerWrapper
 - klass: 'com/ss/ss/register/log/LoggerWrapper'
RDI=0x00007f54381c0190 is pointing into the stack for thread: 0x00007f5274019800
R8 =0x00000007844e4e60 is an oop
com.ss.ss.register.log.LoggerWrapper
 - klass: 'com/ss/ss/register/log/LoggerWrapper'
R9 =0x00000000d8330ea8 is an unknown value
R10=0x0000000000000000 is an unknown value
R11=0x00000000d82502e5 is an unknown value
R12=0x0000000000000000 is an unknown value
R13=0x00000006c1430cc0 is an oop
java.util.concurrent.locks.ReentrantLock$NonfairSync
 - klass: 'java/util/concurrent/locks/ReentrantLock$NonfairSync'
R14=0x0000000000000007 is an unknown value
R15=0x00007f5274019800 is a thread

Internal exceptions (10 events):
Event: 150.590 Thread 0x00007f54853c2000 Exception <a 'java/io/FileNotFoundException'> (0x0000000788d79770) thrown at [/RE-WORK/workspace/8-2-build-linux-amd64/jdk8u45/3457/hotspot/src/share/vm/prims/jni.cpp, line 709]
Event: 150.709 Thread 0x00007f54853c2000 Exception <a 'java/security/PrivilegedActionException'> (0x000000078b0adf78) thrown at [/RE-WORK/workspace/8-2-build-linux-amd64/jdk8u45/3457/hotspot/src/share/vm/prims/jvm.cpp, line 1382]
Event: 150.709 Thread 0x00007f54853c2000 Exception <a 'java/security/PrivilegedActionException'> (0x000000078b0ae2c0) thrown at [/RE-WORK/workspace/8-2-build-linux-amd64/jdk8u45/3457/hotspot/src/share/vm/prims/jvm.cpp, line 1382]
Event: 150.710 Thread 0x00007f54853c2000 Exception <a 'java/security/PrivilegedActionException'> (0x000000078b0af028) thrown at [/RE-WORK/workspace/8-2-build-linux-amd64/jdk8u45/3457/hotspot/src/share/vm/prims/jvm.cpp, line 1382]
Event: 150.710 Thread 0x00007f54853c2000 Exception <a 'java/security/PrivilegedActionException'> (0x000000078b0af370) thrown at [/RE-WORK/workspace/8-2-build-linux-amd64/jdk8u45/3457/hotspot/src/share/vm/prims/jvm.cpp, line 1382]
Event: 150.716 Thread 0x00007f54853c2000 Exception <a 'java/io/FileNotFoundException'> (0x000000078b132510) thrown at [/RE-WORK/workspace/8-2-build-linux-amd64/jdk8u45/3457/hotspot/src/share/vm/prims/jni.cpp, line 709]
Event: 150.717 Thread 0x00007f54853c2000 Exception <a 'java/io/FileNotFoundException'> (0x000000078b133880) thrown at [/RE-WORK/workspace/8-2-build-linux-amd64/jdk8u45/3457/hotspot/src/share/vm/prims/jni.cpp, line 709]
Event: 150.718 Thread 0x00007f54853c2000 Exception <a 'java/io/FileNotFoundException'> (0x000000078b141278) thrown at [/RE-WORK/workspace/8-2-build-linux-amd64/jdk8u45/3457/hotspot/src/share/vm/prims/jni.cpp, line 709]
Event: 153.618 Thread 0x00007f5485375800 Implicit null exception at 0x00007f5476db1064 to 0x00007f5476db1551
Event: 216.372 Thread 0x00007f5274019800 Implicit null exception at 0x00007f54769083ee to 0x0000000000000000

看报错集中在LoggerWrapper,这是一个自己封装的Logger类,可以保存msgId等,需要每次打印日志都要打印出来的东西,避免,每次都需要在后面加上这样的参数。

看使用方法

@ServiceImplementation
public class ProvisioningServiceImpl implements ProvisioningService {
private static final Logger LOGGER = LoggerFactory.getLogger(ProvisioningServiceImpl.class);
private LoggerWrapper loggerWapper;
@ServiceSetter
private CatsProxy userIndexService;
@Override
public ProvisioningResult process(RequestExtArgs extArgs) {
        ProvisioningResult result = new ProvisioningResult();
        result.setRespCode(200);
        result.setRespDesc("success!");

        ProvisioningArgs provisioningArgs = BeanUtil.argsBuild(extArgs.getBody(), ProvisioningArgs.class, extArgs.isBodyJson());
        loggerWapper = new LoggerWrapper(xxx

ProvisioningServiceImpl 是对于service的一个单例,会在服务启动时初始化
分析:每个线程都会访问单例的ProvisioningServiceImpl ,每次都会给全局的loggerWapper new一个新的对象,压力上来时,jvm运行的时候总是进行指针的切换

解决方法

LoggerWrapper作为一个局部变量每次访问LoggerWrapper的时候都重新new一个.

相关文章

  • 一次jvm崩溃分析

    看报错集中在LoggerWrapper,这是一个自己封装的Logger类,可以保存msgId等,需要每次打印日志都...

  • jvm间歇性崩溃分析

    1 问题描述 某服务有两台机器,每隔几天会报警load高,一开始看监控发现gc时间抖动很大,以为是发生了fullg...

  • JVM致命错误日志(hs_err_pid.log)分析

    最近两天测试环境有一个服务总是会挂(两到三天一次),JVM虚拟机总是会崩溃。所以有必要了解JVM崩溃的原因是什么。...

  • JVM问题排查实战系列

    JVM问题排查实战 记一次频繁FGC的简单排查 一次JVM GC长暂停的排查过程 如何使用MAT进行内存泄露分析

  • Android 中级(待续)

    SurfaceView 蓝牙 Android Binder 机制-JVM-JVM源码分析之JVM启动流程 Art ...

  • iOS 符号化闪退日志

    iOS分析崩溃日志 二 iOS应用崩溃日志分析 iOS崩溃crash大解析

  • Jvm优化技术

    Jvm优化技术有:逃逸分析、方法内联 一:Jvm优化技术之逃逸分析 1:概念 JVM的优化技术,可以有效减少Jav...

  • jvm 内存分区及回收

    近期由于jvm经常出现full gc导致jvm崩溃,从日志上查看是Eden和survivor from,to相关的...

  • 【转载】JVM推荐参数

    JVM参数设置、分析关键业务系统的JVM启动参数推荐

  • 高级Java开发面试常用题的答案2

    三、JVM · JVM堆的基本结构。 java_heap_struct.jpg 参考阅读:JVM内存堆布局图解分析...

网友评论

      本文标题:一次jvm崩溃分析

      本文链接:https://www.haomeiwen.com/subject/sbwbcftx.html