Multiple DapIF Instances Locking Error
(Doc ID 2807146.1)
Last updated on SEPTEMBER 27, 2021
Applies to:Oracle Communications Network Charging and Control - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
On Oracle Communications Network Charging and Control (NCC) 184.108.40.206.0 version, Data Pack,
Customer is going to scale up the number of instances of dapIF being run due to load - similar like updating the SLEE with more instances, and using the InterfaceHandle array to use the new instances.
Example, InterfaceHandle = [ "dapIF0" , "dapIF1" , "dapIF2" ].
However, it is observed that under load DAP starts logging below errors about its access to the pending queue:
Is this because the pendingRequests.db sqlite database doesn't handle concurrent access particularly well?
There is a configuration parameter that can be updated ("pendingQueueInMemory"), however they want to understand if this is necessary or not. Is there any other impact other than the loss of persistence of requests, i.e. a crash or shutting down the SLEE will mean any pending requests are lost?
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