Oracle WebLogic Server Support Pattern: Troubleshooting Out of Memory and Memory Leak Problems
(Doc ID 877172.1)
Last updated on JULY 20, 2024
Applies to:
Oracle WebLogic Server - Version 10.3.6 and later Information in this document applies to any platform.
Purpose
This document is a support pattern detailing how to troubleshoot and fix memory leak and other memory related problems
Problem Description
Out Of Memory (OOM): An Out of Memory error occurs due to memory exhaustion, either in java heap or native memory. In the JVM, OOM errors are thrown when the JVM cannot allocate an object because it is out of heap memory, and no more heap memory could be made available by the garbage collector.
Memory Leak: A memory leak occurs if memory is used by an application and not released by the application when it is finished with it. A memory leak can occur in either java heap or native memory, and either will eventually cause an out of memory situation.
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!
