IScript Which Uses Out of Box Function "HashClear" Consumes too Much Memory
(Doc ID 2671490.1)
Last updated on MAY 24, 2020
Applies to:
Oracle Communications Billing and Revenue Management - Version 7.5.0.17.0 and laterInformation in this document applies to any platform.
Symptoms
Issue is that an iScript which uses out of box function hashClear consumes too much memory and does not release memory while reloading data by semaphore. It was observed that loading data by iScript having this function takes more memory (even if reading from the database during startup). As a result, pipeline shuts down due to reaching 95% memory utilization (memory monitor has been set).
Steps to reproduce:
- Comment hashClear function in the iScript
- Start pipeline
- Check memory
- Reload iScript using “ifw.Pipelines.PRE_PROCESS.Functions.PreProcessing.FunctionPool.Map_IMSI.Module.Reload {}”
- Stop pipeline
- Uncomment hashClear function in the iScript
- Start pipeline
- Check memory
- Reload iScript using “ifw.Pipelines.PRE_PROCESS.Functions.PreProcessing.FunctionPool.Map_IMSI.Module.Reload {}”
- Compare results
Notice that memory consumption in case 2 is higher.
Changes
Cause
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
Symptoms |
Changes |
Cause |
Solution |
References |