Admin Server Crashes after WebLogic Upgrade (Doc ID 2836333.1)

Last updated on DECEMBER 16, 2023

Applies to:

Symptoms

Admin Server Crashes with the below error after WebLogic Upgrade.

#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00002b63d632b079, pid=30402, tid=0x00002b640552b700
#
# JRE version: Java(TM) SE Runtime Environment (8.0_311-b25) (build 1.8.0_311-b25)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.311-b25 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C [libc.so.6+0x4d079] _IO_vfprintf+0x4a79
#
# Core dump written. Default location: <PATH_TO_CORE_FILE>/core or core.30402
#
# An error report file with more information is saved as:
# <PATH_TO_PID_LOG>/hs_err_pid30402.log
#
# If you would like to submit a bug report, please visit:
# http://bugreport.java.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
./startWebLogic.sh: line 202: 30402 Aborted (core dumped) ${JAVA_HOME}/bin/java ${JAVA_VM} ${MEM_ARGS} ${LAUNCH_ARGS} -Dweblogic.Name=${SERVER_NAME} -Djava.security.policy=${WLS_POLICY_FILE} ${JAVA_OPTIONS} ${PROXY_SETTINGS} ${SERVER_CLASS}
Stopping Derby server...
Derby server stopped.

Changes

 WebLogic Upgraded from one version to another

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.