My Oracle Support Banner

WebLogic Server Support Pattern: Binary Core File Analysis (Doc ID 779344.1)

Last updated on OCTOBER 04, 2021

Applies to:

Oracle WebLogic Server - Version 6.1 and later
Information in this document applies to any platform.
***Checked for relevance on 28-Jun-2016***

Purpose

Problem Description

An application gets a binary core file produced when the WebLogic Server process terminates due to some invalid native core (machine specific code). A server crash, JVM crash, machine crash, or HotSpot error may also be associated with this occurrence. This article will describe what steps are needed to gather information from a core file on various platforms.

Problem Troubleshooting

Please note that not all of the following items would need to be done. Some issues can be solved by only following a few of the items.

Troubleshooting Steps

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
Purpose
 Problem Description
 Problem Troubleshooting
Troubleshooting Steps
 Why does the problem occur?
 Gathering Core information from: SOLARIS
 Gathering Core information from: LINUX
 Gathering Core information from: HPUX
 Gathering Core information from: AIX
 Gathering Core information from: WINDOWS
 What if I don't have a Debugger?
 Operating System Values that should be checked for core file generation
 Core Files due to JIT Compiler
 Stop the JVM to get Thread Dumps
 On-line Debugger Manuals
 Need further help?

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