OC4J JVM Crashes Randomly with Error in $ORACLE_HOME/opmn/logs/... "Unexpected Exception Has Been Detected In Native Code Outside The VM. Signal 4"
Last updated on MARCH 08, 2017
Applies to:Oracle Containers for J2EE - Version 188.8.131.52.0 to 10.1.2.2.0 [Release AS10g to AS10gR2]
Oracle Solaris on SPARC (64-bit)
***Checked for relevance on 24-Jan-2013***
***Checked for relevance on 08-DEC-2014***
The problem documented here was reported for Oracle AS 10g on Solaris 9.
It specifically affected the oc4j JVM.
Java version 1.4.1_03-b02
OC4J JVM crashed randomly.
The process was just restarted by opmn and continued working normally.
The only info found in reference to crash was,
from [ $ORACLE_HOME/opmn/logs/OC4J~external~default_island~1 ] :
An unexpected exception has been detected in native code outside the VM.
Unexpected Signal : 4 occurred at PC=0xF6805874
NOTE: We are unable to locate the function name symbol for the error
just occurred. Please refer to the release note documentation for possible
reason and solutions.
Current Java thread:
Local Time = Mon Nov 8 14:53:04 2004
Elapsed Time = 17129
# The exception above was detected in native code outside the VM
# Java VM: Java HotSpot(TM) Server VM (1.4.1_03-b02 mixed mode)
# An error report file has been saved as hs_err_pid26110.log.
# Please refer to the file for further information.
notice: Unexpected Signal : 4 in unix this signal means --- SIGILL (Illegal instruction) ---
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms