My Oracle Support Banner

With Timeout Event Raised, ASAP Stops Processing Work Orders if WO_TIMEOUT_EVENT_TWICE is Set to 0 (Doc ID 1901928.1)

Last updated on JULY 06, 2022

Applies to:

Oracle Communications ASAP - Version 7.0.2 and later
Information in this document applies to any platform.


When a batch of work orders (about 5000 WOs) are sent with timeout of 40 seconds per order, the following occurs:

It was observed that the work orders accumulate in the pending queue, which is the expected behavior because the NE has limited connections and there are 5 devices configured for that NE.

The expected result for this scenario would be that ASAP started to put pending work orders in timeout state because the NE cannot respond to ASDL commands fast enough to avoid WOs accumulating.

The problem is that when timeout events are raised, ASAP stops processing work orders. We saw that work orders were no longer inserted in the pending queue and they would stay in SARM database in the INIT state.

The work orders in pending queue weren't be processed until the NEP was restarted manually.




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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.