My Oracle Support Banner

RatedEventFormatter Crashes and Unable to Process Backlog (Doc ID 2629471.1)

Last updated on JANUARY 22, 2020

Applies to:

Oracle Communications BRM - Elastic Charging Engine - Version 11.3.0.9.0 and later
Information in this document applies to any platform.

Goal

The out of the box Java Virtual Memory (JVM) settings were causing the RatedEventFormatter (REF) to crash, this prompted the user to increase the heap to 32GB from the 1M NoSQL session test.
After removed many of the settings, there are still some old parameters being used when starting the JVM with Elastic Charging Engine (ECE). 

Virtual Memory (VM) Flags:
Non-default VM flags: -XX:NumberOfGCLogFiles=4 +PrintAdaptiveSizePolicy


Please explain how to remove these?
#Original settings
#options=-Xms12g -Xmx12g -XX:SurvivorRatio=2 -XX:+UseG1GC -XX:+AlwaysPreTouch -XX:MaxGCPauseMillis=80 -XX:ParallelGCThreads=4 -XX:+ExplicitGCInvokesConcurrent -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:-PrintGCTimeStamps -XX:+PrintTenuringDistribution -XX:+PrintAdaptiveSizePolicy -Xloggc:/opt/ece/logs/G1Logs/$Node_GC.log -Dcom.sun.management.jmxremote.authenticate=false -Dtangosol.coherence.security=false
#------------------
# Tested at 32G ok
#options=-Xms32g -Xmx32g -XX:SurvivorRatio=2 -XX:+UseG1GC -XX:+AlwaysPreTouch -XX:MaxGCPauseMillis=80 -XX:ParallelGCThreads=4 -XX:+ExplicitGCInvokesConcurrent -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:-PrintGCTimeStamps -XX:+PrintTenuringDistribution -XX:+PrintAdaptiveSizePolicy -Xloggc:/opt/ece/logs/G1Logs/$Node_GC.log -Dcom.sun.management.jmxremote.authenticate=false -Dtangosol.coherence.security=false
#------------------
# setting to 8G as requested by support
options=-Xms8g -Xmx8g -XX:+UnlockExperimentalVMOptions -XX:+UseG1GC -XX:+AlwaysPreTouch -XX:G1HeapRegionSize=4m -XX:ConcGCThreads=1 -XX:ParallelGCThreads=4 -XX:+ExplicitGCInvokesConcurrent -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:-PrintGCTimeStamps -XX:+PrintTenuringDistribution -Xloggc:/opt/ece/logs/G1Logs/$Node_GC.log -Dcom.sun.management.jmxremote.authenticate=false -Dtangosol.coherence.security=false

 
Please recommend production parameters required to support 100% load over 10 hours at 13 Millions (M) per hour.
3.6M in 22 minutes is an expected load of processing. However, looking at the jConsole, the heap usage climbed to 100% from 13:35 to 13:40.



 

Solution

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
Goal
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.