Hi,

We're running on WebSphere 7 and 8 on ND and with a Java HotSpot on Solaris OS.

We ran into a SIGSEV error that we are not sure the cause.

Error:

# An unexpected error has been detected by HotSpot Virtual Machine:

# SIGSEGV (0xb) at pc=0xffffffff7d43b6a8, pid=28289, tid=2914

# Java VM: Java HotSpot(TM) 64-Bit Server VM (xxxxx- mixed mode)

From what we see, there is no application error or WebSphere error in the systemout.log that could lead to the java crash. We found that there is a memory leak from the native_stdout but we are not sure how that would result in a SIGSEV error.

Appreciate your feedback on this.

SIGSEV errors related to Java HotSpots can happen for various reasons and are not tied to a product such as WebSphere. They are Java related issues and they can occur as a result of insufficient swap space, corrupt jar files, hardware issues etc. Your error is most likely caused by a corrupted jar file based on the description(stack) you have shared.

Take a look at the technote below on how to resolve the error.

JVM crashes due to corrupted JAR file :

https://www.ibm.com/support/pages/jvm-crashes-due-corrupted-jar-file

Another reference worth reviewing is the stackoverflow question asked here:

A fatal error has been detected by the Java Runtime Environment: SIGSEGV, libjvm:

https://stackoverflow.com/questions/6448163/a-fatal-error-has-been-detected-by-the-java-runtime-environment-sigsegv-libjvm