ASAP Is Not Spawning All The Available Connections Even Though Pending Queue Size Is Very High (Doc ID 2005122.1)

Last updated on MAY 05, 2015

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.


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:

>> 084604.180:52:SANE:ASDL Dispatch            :4017:sarm/sarm/sarm/nep_driver.c
'NE_NAME': State: 0 Pending 976 In Proc 2 Connect 20 Prime 1


2. There are lots of 'ASDL Rejected' appearing  in the SARM daig file (see below). 'ASDL Rejected' message can be seen in the SARM diag file as follows:

grep "ASDL Rejected by" converted/sarm.diag |wc -l

SARM diag:

>> 140729.578:52:SANE:Send ASDL                :4637:sarm/sarm/sarm/nep_driver.c   
G0944596703_500_2015040114065906: ASDL ASDL_NAME for SRQ 30767, ASDL Rejected by 'NE_NAME'

3. In the JNEP diag file, we see similar messages (as follows) appearing if a RETRY_DIS is triggered:

$ grep RETRY_DIS JNEP* | grep DEBUG

JNEP_NAME.diag.031129:com.mslv.activation.cartridge: (DEBUG) Exit Type: RETRY_DIS Description: Connection reset
JNEP_NAME.diag.042956:com.mslv.activation.cartridge: (DEBUG) Exit Type: RETRY_DIS Description: Connection reset
JNEP_NAME.diag.062829:com.mslv.activation.cartridge: (DEBUG) Exit Type: RETRY_DIS Description: Connection reset

4. While performing an 'asap_utils' option 30 , it shows other devices are free and not bound , however  spawning is not happening.


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms