Java.storeNARWithAbsoluteTimer(out, TableIndex, FlushTimeLong) Not Flusing at Specified Time
(Doc ID 2818031.1)
Last updated on OCTOBER 31, 2021
Applies to:Oracle Communications Offline Mediation Controller - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
Customer have out of box Aggregation Processor (AP) which uses flush based on Application Programming Interface (API) Java.storeNARWithAbsoluteTimer(out, tableIndex, flushTimeLong);
flushTimeLong will have timeinmillisecs as shown below. It is expected to flush at the time occurs but AP is not flushing at the time expected but it is taking time configured on GUI to flush.
flushTimeLong = 1635145800000;
Date and time (GMT): Monday, 25 October 2021 07:10:00
In above example if on GUI flush time is given as 3600 and if we pass flushTimeLong as 1635145800000 and we use only storeNARWithAbsoluteTimer and no other API, it is expected to flush at the time 25 October 2021 07:10:00 but it flushes after 3600 seconds.
Followings are the use cases:
- Configured AP Graphical User Interface (GUI) timer 10 minutes,
- Configured AbsoluteTimer in Node Programming Language (NPL) for 5 minutes,
- Process the NAR files
Outcome: It is consider only GUI timer for flushing not the AbsoluteTimer configured in NPL for 5 minutes
- Configured GUI timer 5 minutes
- Configured AbsoluteTimer in NPL for 10 minutes
- Process the Network Accounting Record (NAR) files
Outcome: It is consider only AbsoluteTimer which is configured in Node Programming Language (NPL) for 10 minutes
What is the correct behavior in these uses cases?
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