Example of how to Troubleshoot a Memory Leak in UCM Custom Components Using VisualVM
(Doc ID 960595.1)
Last updated on MAY 22, 2020
Applies to:Oracle WebCenter Content - Version 10.0 and later
Information in this document applies to any platform.
checked for currency 25-JUL-2013
A difficult area to troubleshoot in UCM is finding memory leaks in custom components. Starting in JDK 6, Update 7, Sun installs a tool called "VisualVM", which is an executable that ships in the JDK bin directory. This tool allows for enhanced visibility of what is taking place within a running JVM. If UCM is using a version of the JDK of Update 7 or greater, this tool can be leveraged effectively in finding memory leaks. The note below gives an overview on how to use this tool. VisualVM can be downloaded separately and installed, or it can be run from the JDK bin directory. The note below describes how to set up UCM to use a specific JDK as well as how to run VisualVM.
<Note 950621.1> Use VisualVM Tools to Troubleshoot UCM and Observe Performance Problems Occurring in Java Virtual Machine
The intention of this note is to show the steps that can be used in narrowing down a memory leak. A custom "Memory Leaker" component was created for this demonstration.
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
Recognizing a Potential Memory Leak
|Watching the Heap Grow|
Using the Memory Profiler to Take Snapshots
Compare Snapshots to See Memory Growth
Examining the Leak Candidate in a Snapshot
Viewing the Leaking Class with a Heap Dump