可以提供一些帮助,
我们的生产服务器突然崩溃,我研究了很多,但没有找到解决方案,除了人们建议升级java,但我们已经在最新补丁(java 6_71)
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00002b5b4dc9c2ba, pid=1278, tid=47671325686080
#
# JRE version: 6.0_71-b12
# Java VM: Java HotSpot(TM) 64-Bit Server VM (20.71-b01 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C [libcknfast.so+0x10f2ba] long double+0x11a
#
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
--------------- T H R E A D ---------------
Current thread (0x00000000590ea800): JavaThread "http-0.0.0.0-8090-2" daemon [_thread_in_native, id=11189, stack(0x00002b5b585ef000,0x00002b5b586f0000)]
siginfo:si_signo=SIGSEGV: si_errno=0, si_code=1 (SEGV_MAPERR), si_addr=0x00000000000001a1
答案 0 :(得分:4)
如果不确切知道问题是什么,请在确定问题的根本原因和解决方案时考虑以下因素。
错误信息实际上解释了很多:
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
有问题的框架是:
# Problematic frame:
# C [libcknfast.so+0x10f2ba] long double+0x11a
“[A]突然开始崩溃”结合此错误信息表明其他可能性:
libcknfast.so
)交互的Java代码。libcknfast.so
)本身的更改。基本上,请考虑您的团队是否部署了更新的Java代码,更新的PKCS11库,JBoss更新,或其他任何更新或配置更改,在问题出现之前,这些更改或配置更改。
此外,还有many SO questions & answers related to “The crash happened outside the Java Virtual Machine in native code.” - 目前超过250个 - 当您考虑在问题发生之前对生产服务器进行可能的更改时,这可能对特定假设有所帮助。
One that caught my attention特别归结为简单地将额外的null
传递给本机函数(即在此类错误的根源处潜在的代码更改的示例); another that caught my attention归结为JVM内存参数(即此类问题的核心可能的配置更改示例)。