Last updated on OCTOBER 17, 2016
Applies to:Oracle Demantra Demand Management - Version 22.214.171.124 and later
Information in this document applies to any platform.
***Checked for relevance on 09-July-2013***
On version 126.96.36.199:
Initially the customer reported that Demantra became unresponsive.
It was found that the Oracle Application Server was crashing with
JVMDUMP006I Processing Dump Event "uncaught", detail "java/lang/OutOfMemoryError" - Please Wait.
Support suggested to make the following changes to opmn.xml
change the current entries to:
value="-Xss512k -ms1280m -mx1280m -XX:PermSize=128m -XX:MaxPermSize=256m
This is keeping up the OAS but the users are still experiencing huge performance problems when creating deductions.
The customer occasionally has to bounce Demantra in order to resume normal responsiveness.
However, when waiting several minutes for the processing to take place, normal behavior returns.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms