OPMN Consuming Memory Over Time with "Process Ping Failed" Messages in Logs
(Doc ID 1376186.1)
Last updated on JANUARY 11, 2017
Applies to:Oracle Fusion Middleware - Version 188.8.131.52.0 to 184.108.40.206.0 [Release Oracle11g]
Oracle Fusion Middleware - Version 220.127.116.11.0 to 18.104.22.168.0 [Release Oracle11g]
Oracle Forms - Version 22.214.171.124.0 to 126.96.36.199.0 [Release 11g]
Oracle Reports Developer - Version 188.8.131.52.0 to 184.108.40.206.0 [Release 11g]
BI Publisher (formerly XML Publisher) - Version 220.127.116.11.0 to 18.104.22.168.0 [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:
- Oracle Fusion Middleware 22.214.171.124.0 installed on any platform.
- Oracle Forms & Reports 126.96.36.199.0 installed on any platform.
- BI Publisher 188.8.131.52.0 installed on any platform.
Steps to Reproduce
1) Configure 184.108.40.206 or 220.127.116.11 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:
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!