Improve order cache ejection logic
(Doc ID 1682409.1)
Last updated on JULY 12, 2024
Applies to:
Oracle Communications Order and Service Management - Version 7.2.2 and laterInformation in this document applies to any platform.
This applies to Order and Service Management 7.2.2 Patch 4 and later.
Symptoms
Log error message
Cache reached and remained above 90% full about a minute ago. Review and tune cache and JVM heap params.
Example:
<Jun 10, 2014 6:43:54 PM CEST> <Warning> <oms> <BEA-000000> <impl.c:
Cache % Full # Orders Information
---------------------- ------ --------- ---------------------------------------------------------------------------------------------------
Closed Order Cache 0% 0/50
Historical Order Cache 0% 0/1000
Orchestration Cache 99% 999/1000 Cache reached and remained above 90% full 5 minutes ago. Review and tune cache and JVM heap params.
Order Cache 100% 1000/1000 Cache reached and remained above 90% full 5 minutes ago. Review and tune cache and JVM heap params.
Redo Order Cache 0% 0/1000
The cache statistics information which is logged periodically, if the cache hits > 90%, the system does not necessarily requires to be retuned (increase the cache size). The messages about the cache being full is just a warning/hint to review your params if being seen frequently in the log file. The tuning depends on a number of factors including amount of memory available, throughput of orders, size of orders, etc.
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 |