Running BPEL Process Causes "java.lang.OutOfMemoryError: Java heap space" - Related to Domain auditLevel and collaxa.cube.xml Logging Level
(Doc ID 950646.1)
Last updated on OCTOBER 08, 2020
Applies to:Oracle(R) BPEL Process Manager 10g - Version 10.1.3.1 to 10.1.3.5.0
Information in this document applies to any platform.
***Checked for relevance on 12-Sep-2011***
***Checked for relevance on 13-Feb-2013***
You are running a BPEL process that after some time results in an out of memory error. You have already tuned the JVM for BPEL by following best practices or a document such as <Note 416818.1> BPEL Server hangs due to "java.lang.OutOfMemoryError" but the out of memory still happens.
Observing the JVM with a monitoring tool such as jvisualvm shows frequent filling of the Eden Space and rapid filling of the Old Gen which is resulting in frequent garbage collections. The container slows and eventually runs out of memory.
The running BPEL process does extensive XML manipulations such as for example the use of While loop(s) that do several Assign activities which are doing copies between variables.
At the time of the error the $OH/opmn/logs/<BPEL Container>.log may show a similar error:
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