My Oracle Support Banner

OPMN Consuming Memory Over Time with "Process Ping Failed" Messages in Logs (Doc ID 1376186.1)

Last updated on MARCH 18, 2024

Applies to:

Oracle Forms - Version to [Release 11g]
Oracle Fusion Middleware - Version to [Release Oracle11g]
Oracle Fusion Middleware - Version to [Release Oracle11g]
Oracle Reports Developer - Version to [Release 11g]
BI Publisher (formerly XML Publisher) - Version to [Release 11.1]
Information in this document applies to any platform.


The OPMN process is consuming too much memory over time which seems like a memory leak. It is a slow leak, over a couple of weeks it will consume 6-8GB of RAM. This affects production and test systems, but after longer up times it is more noticeable. It is important to catch this problem before going production. This affects the following products:

Steps to Reproduce

1) Configure or instance.
2) Start instance with OPMN, "opmnctl startall"
3) Monitor OPMN process over time for memory leak.

Applications may slow or hang, and errors referring to memory problems may result.

The opmn process will contimnue to increase in memory size

The command "opmnctl debug comp=ons"  will show all Pool Counts equal to 1

The following is observed on the opmn/logs/opmn.log file:

[TRACE:1][][OPMN][code:libopmncustom]Process Ping Failed


Restarting OPMN frequently:

opmnctl stopall

opmnctl startall




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

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