SOA Serves Crashed With Dump File
(Doc ID 2544959.1)
Last updated on JANUARY 08, 2024
Applies to:
Oracle SOA Suite - Version 11.1.1.7.8 and laterInformation in this document applies to any platform.
Symptoms
SOA servers crashed all of sudden and created dump file
ERROR
-----------------------
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0xffffffff719e4be0, pid=25473, tid=374
#
# JRE version: 7.0_15-b03
# Java VM: Java HotSpot(TM) 64-Bit Server VM (23.7-b01 mixed mode solaris-sparc compressed oops)
# Problematic frame:
# J oracle.j2ee.ws.wsdl.extensions.AbstractSerializer.startMarshall(Ljavax/wsdl/Definition;Loracle/j2ee/ws/wsdl/util/XMLWriter;Ljavax/wsdl/extensions/ExtensibilityElement;)V
#
# Core dump written. Default location: /reuters/oracle/product/soa/11g/fmw/admin/SOACoreDomain/mserver/SOACoreDomain/core or core.25473
#
# An error report file with more information is saved as:
# /reuters/oracle/product/soa/11g/fmw/admin/SOACoreDomain/mserver/SOACoreDomain/hs_err_pid25473.log
[thread 373 also had an error]
#
# If you would like to submit a bug report, please visit:
# http://bugreport.sun.com/bugreport/crash.jsp
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 |
| References |