How To Prevent ASDL Queuing For Connections To NE
(Doc ID 1126677.1)
Last updated on DECEMBER 03, 2019
Applies to:Oracle Communications ASAP - Version 4.7.1 to 7.0.1 [Release 4.7 to 7.0.0]
Information in this document applies to any platform.
If two ASDLs for an NE are generated is there anyway to ensure the second ASDL is not queued behind the first?
Setting SPAWN_THRESHOLD to zero appears to work but is not documented.
Is Setting SPAWN_THRESHOLD to zero supported?
If not supported, then it seems the best we can manage is to set the SPAWN_THRESHOLD to 1, the KILL_THRESHOLD to 0 and the DROP_TIMEOUT to a very large number then hope at some point in time the SPAWN_THRESHOLD is exceeded.
Are there other solutions?
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