WebCenter Server Core Dumps when using Java HotSpot Virtual Machine (Doc ID 1514563.1)

Last updated on OCTOBER 14, 2023

Applies to:

Purpose

Java HotSpot Virtual Machine, a core component of Oracle's Java SE platform, core dumps (resulting in a server crash) while optimizing certain methods in Oracle WebCenter. Errors similar to the one below are reported:

# A fatal error has been detected by the Java Runtime Environment:

#
# SIGSEGV (0xb) at pc=0xffffffff7318caf0, pid=19921, tid=149
#
# JRE version: 6.0_29-b11
# Java VM: Java HotSpot(TM) 64-Bit Server VM (20.4-b02 mixed mode solaris-sparc compressed oops)
# Problematic frame:
# J org.apache.myfaces.trinidadinternal.context.RequestContextImpl.addPartialTriggerListeners(Ljavax/faces/component/UIComponent;[Ljava/lang/String;)V
#
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
#

--------------- T H R E A D ---------------

Current thread (0x00000001145ba000): JavaThread "[ACTIVE] ExecuteThread: '13' for queue: 'weblogic.kernel.Default (self-tuning)'" daemon [_thread_in_Java, id=149, stack(0xfffffffea6800000,0xfffffffea6900000)]

siginfo:si_signo=SIGSEGV: si_errno=0, si_code=1 (SEGV_MAPERR), si_addr=0x0000000000000000

Registers:
G1=0xffffffff503d5098 G2=0x00000001145ba000 G3=0xffffffff73516254 G4=0x00000000000000d1
G5=0xfffffffed48e36e8 G6=0xfffffffec03fe000 G7=0xfffffffea7804200 Y=0x0000000000000000
O0=0x0000000000000000 O1=0x0000000000efb20d O2=0xffffffff73547c80 O3=0xfffffffec0412950
O4=0xffffffff5049e798 O5=0xfffffffea68f6a11 O6=0xfffffffea68f6a11 O7=0xffffffff7318cae8
L0=0x0000000000000001 L1=0x0000000000000000 L2=0x000000007fffffff L3=0x0000000002053859
L4=0x0000000011ffae13 L5=0xffffffff7318c4b0 L6=0xff7fffff721fe000 L7=0xffffffff503d5098
I0=0x00000000159ac43f I1=0x0000000000000002 I2=0xffffffff6dae05f0 I3=0xffffffff6d1601f8
I4=0x0000000000000007 I5=0x0000000000000002 I6=0xfffffffea68f6af1 I7=0xffffffff732c032c
PC=0xffffffff7318caf0 nPC=0xffffffff7318caf4 

Use the steps in the document below to identify the culprit method responsible for the server crash:
   Note: 1009131.1 - How to Determine the Methods Compiled Before a JVM Crash

Once the method is determined, it can be excluded from optimization at runtime by executing the steps below ("Details").

Scope

This document only applies to a Fusion Middleware environment where Oracle's Java SE platform is used (Java HotSpot Virtual Machine).
Steps documented here-in do not apply to a Fusion Middleware environment where Oracle JRockit is used.

Details