ASAP Is Not Spawning All The Available Connections Even Though Pending Queue Size Is Very High
(Doc ID 2005122.1)
Last updated on DECEMBER 21, 2023
Applies to:
Oracle Communications ASAP - Version 7.0.1 to 7.0.2 [Release 7.0.0]Information in this document applies to any platform.
Symptoms
ASAP is not able to spawn all the available devices. JNEP process is unable to process orders and orders are pending in status 103 on SARM in production.
1. In the SARM diag file, the pending queue is high but the 'In Proc' queue is much less than the number of connections (see below).
SARM diag:
4. While performing an 'asap_utils' option 30 , it shows other devices are free and not bound , however spawning is not happening.
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 |