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

Last updated on MARCH 18, 2024

Applies to:

Symptoms

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:

• Oracle Fusion Middleware 11.1.1.5.0 installed on any platform.
• Oracle Forms & Reports 11.1.2.0.0 installed on any platform.
• BI Publisher 11.1.1.5.0 installed on any platform.

Steps to Reproduce

1) Configure 11.1.2.0 or 11.1.1.5 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

Workarounds

Restarting OPMN frequently:

opmnctl stopall

opmnctl startall

Cause

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