Oracle Service Bus Hard Crash After Hours Of Restarting " weblogic.nodemanager.NMService.rotateLogFiles"
(Doc ID 2934724.1)
Last updated on MAY 06, 2024
Applies to:
Oracle Service Bus - Version 12.2.1.3.0 and laterInformation in this document applies to any platform.
Symptoms
OSB Managed Server Java Virtual Machine Crashed due to Nodemanager of Weblogic Server, Specifically during File Rotation
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007f79258fffc9, pid=14292, tid=0x00007f77a2d87700
#
# JRE version: Java(TM) SE Runtime Environment (8.0_301-b25) (build 1.8.0_301-b25)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.301-b25 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C [libc.so.6+0xc0fc9] readdir+0x29
R14=0x00007f77a308e498: logFileDir+0 in /u01/app/oracle/product/soa/12.2.1/wlserver/server/native/linux/x86_64/libnodemanager.so at 0x00007f77a2e89000
..
Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
j weblogic.nodemanager.NMService.rotateLogFiles0(Ljava/lang/String;IILjava/lang/String;IILjava/lang/String;Ljava/lang/String;)V+0
j weblogic.nodemanager.NMService.access$1300(Lweblogic/nodemanager/NMService;Ljava/lang/String;IILjava/lang/String;IILjava/lang/String;Ljava/lang/String;)V+14
j weblogic.nodemanager.NMService$1.run()V+71
v ~StubRoutines::call_stub
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |