My Oracle Support Banner

How to Change eWay Max Heap Size because of Message Not Flowing Due to java.lang.OutOfMemoryError (Doc ID 1434251.1)

Last updated on DECEMBER 04, 2019

Applies to:

Oracle Retail Integration Bus - Version 12.0.9 and later
Information in this document applies to any platform.
Checked for relevance on August 27th, 2013


As reported in this specific case, ASNOUT Message are not flowing from RWMS to RMS
There are records within table BOL_TO_UPLOAD, but it is not publishing from this table

The following was found in ewASNOutFromRDMWH1 log files:

AlertPublisher className = com.retek.rib.sbyn.alert.EGateAlertPublisher
JVMDG217: Dump Handler is Processing a Signal - Please Wait.
JVMDG315: JVM Requesting Heap dump file
JVMDG318: Heap dump file written to /vol01/egate/5.0.5/heapdump737344.1331410957.txt
JVMDG303: JVM Requesting Java core file
JVMDG304: Java core file written to /vol01/egate/5.0.5/javacore737344.1331410960.txt
JVMDG215: Dump Handler has Processed Outofmemory Signal -1.

This indicates that the Max Heap Size needs to be increased. This is generally due to increased message size and not enough memory available to process successfully.

How to achieve this ?


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.