How to Identify and Avoid Out Of Memory Problems Caused by Non-trivial finalize()
(Doc ID 1328761.1)
Last updated on MAY 18, 2023
Applies to:
Oracle WebLogic Server - Version 8.1 and laterInformation in this document applies to any platform.
Goal
This document describes how to find the point of cause which produces the Out Of Memory (OOM) issues caused by using the non-trivial finalizer. Simply, the trivial means no explicit finalize() in the class, non-trivial is opposite.
Sometimes, for improper usage of the finalize() method in an application, the Java Virtual Machine (JVM) might throw the OOM exception, in which is the OOM is caused by non-trivial finalizer.
Note:
Most of the cases of OOM had been described in <Document 877172.1> which does not discuss about this specific type of OOM caused by non-trivial Finalizer.
This document is specific to SUN JVM.
Most of the cases of OOM had been described in <Document 877172.1> which does not discuss about this specific type of OOM caused by non-trivial Finalizer.
This document is specific to SUN JVM.
Solution
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
| Goal |
| Solution |
| References |