-
Notifications
You must be signed in to change notification settings - Fork 24.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JVM is crashing with SIGSEGV #9022
Comments
SEE THE FULL ERROR FILE - http://pastebin.com/i7hQ27P2 A fatal error has been detected by the Java Runtime Environment: SIGSEGV (0xb) at pc=0x00007fe5d29c0fa6, pid=1472, tid=140624657848064 JRE version: Java(TM) SE Runtime Environment (7.0_72-b14) (build 1.7.0_72-b14) Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again If you would like to submit a bug report, please visit: --------------- T H R E A D --------------- Current thread (0x00007fe54c8c9800): JavaThread "elasticsearch[Alexander Goodwin Pierce][transport_client_worker][T#7]{New I/O worker #7}" daemon [_thread_in_Java, id=2497, stack(0x00007fe5bab71000,0x00007fe5bac72000)] siginfo:si_signo=SIGSEGV: si_errno=0, si_code=2 (SEGV_ACCERR), si_addr=0x00007fe5cd898000 Registers: Top of Stack: (sp=0x00007fe5bac6fbf0) Instructions: (pc=0x00007fe5d29c0fa6) Register to memory mapping: RAX=0x0000000000000000 is an unknown value
Stack: [0x00007fe5bab71000,0x00007fe5bac72000], sp=0x00007fe5bac6fbf0, free space=1018k Java frames: (J=compiled Java code, j=interpreted, Vv=VM code) |
@rmuir any ideas here? |
Can you install debug symbols for JVM and libc? With that the traces will atleast be meaningful. Eg. installing [package]-dbg on debian env will give you the debug symbols. Also, depending on what environment you are running in, it may be possible to configure it to take a core-dump on SIGSEGV. On GNU/Linux, try running 'ulimit -c unlimited' before launching tomcat. Check for presence of file /core after crash. |
I'm running an Spring application on the Tomcat which is connecting to ES 1.2.1. Tomcat JVM is crashing from time to time with the following error.
The text was updated successfully, but these errors were encountered: