On 6/25/2018 9:20 PM, Prateek wrote: > My configuration: > OS:REDHAT 7.5 (64 bit) > Tomcat: 8.5.31 > Jdk- jdk-11(Early-Access)
+1 to everything else you've been told on this thread. More stuff inline below. > When I am trying to start my server I got following error as: > A fatal error has been detected by the Java Runtime Environment: > # > # SIGSEGV (0xb) at pc=0x00007fd4f206e28a, pid=2412, tid=2412 > # > # JRE version: (11.0+18) (build ) > # Java VM: Java HotSpot(TM) 64-Bit Server VM (11-ea+18, mixed mode, aot, > sharing, tiered, compressed oops, g1 gc, linux-amd64) > # Problematic frame: > # C [libc.so.6+0x8128a] strlen+0x2a This is saying that the segfault occurred in libc code, specifically the strlen function. This suggests that either the JVM is using the libc library incorrectly, or that the libc library on your system is bad. > # An error report file with more information is saved as: > # /localdisk/corefiles/hs_err_pid2412.log Can you provide the JVM error file above (or the one from the most recent crash)? > Saved corefile core.2412 If I had any idea how to interpret coredumps, I would ask for that file, but I don't. Maybe Oracle can do something useful with it. I did find a JDK bug showing a crash in libc, but that bug should be fixed in Java 9 and later. https://bugs.openjdk.java.net/browse/JDK-8186817 If the behavior is exactly the same with Java 10, then I would think it means the system itself has a problem. My first thought would be that the kernel or system libraries like libc are broken, but it could also be faulty hardware. Can you get this working if you put Java 8 on THIS system and use that? Thanks, Shawn --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
