ASAP Orders Are Getting Stuck Frequently With RPC Failure errcode in NEP
(Doc ID 1672875.1)
Last updated on AUGUST 31, 2020
Applies to:Oracle Communications ASAP - Version 5.0.0 and later
Information in this document applies to any platform.
***Check on Currency on Mar 9 2017***
ASAP orders are getting stuck. This requires the user to stop and then start ASAP to process the order. asap_utils -d 7 is showing "Connecting not available". After restart of ASAP, it is showing "Available".
NEP diagnostic file shows the following error:
This only happened after more than an hour of connection inactivity for the SARM connection pool. So it looks like there is a timeout somewhere between the SARM database and the ASAP.
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