Information

Title	Loading large JSON object results in DBDOWN due to the Broker being killled

URL Name	dbdown-oom-killer-client-loading-large-json-object

Article Number	000110301

Environment	Product: OpenEdge Version: 11.6, 11.7 OS: Linux Other: AppServer, PASOE

Question/Problem Description

Database lost the primary Broker process and was automatically shutdown with the errors (4194).

Linux system messages log file reveals the following:

kernel: _proapsv invoked oom-killer: gfp_mask=0x10200da, order=0, oom_score_adj=0

Steps to Reproduce

Clarifying Information

Error Message	(-----) Database broker PID is dead. tag: BROKER_PID error:-1309 Broker disappeared, updating <dbname>.lk file. (4194)

Defect Number	Defect PSC00361837

Enhancement Number

Cause

In OpenEdge 11.6 and 11.7 FCS versions, there is a memory leak issue with Progress Clients (_progres, _proapsv, prowin) when using JSON objects. As soon as the Linux Kernel runs out of memory, once old page frames have been reclaimed, the OOM killer kicks in and starts 'kill or sacrifice child' to keep the OS itself operational and prevent kernel panic.

Excessive memory usage parsing JSON object

Resolution

Upgrade to OpenEdge 11.7.3, 12.0 where the memory leak has been fixed.

Alternatively this issue is included the following Generally Available Hotfixes:

OpenEdge 11.7.1.009
OpenEdge 11.7.2.004

Workaround

Notes

Progress Articles:

Would consuming all memory bring other databases down?
What is the OOM Killer (Out of Memory Killer)?

Keyword Phrase

Last Modified Date	11/20/2020 7:10 AM

Loading large JSON object results in DBDOWN due to the Broker being killled

Information