Weblogic Threads Stuck While Processing Work Order In ASAP
(Doc ID 1353424.1)
Last updated on FEBRUARY 21, 2019
Applies to:Oracle Communications ASAP - Version 5.2.4 and later
Information in this document applies to any platform.
***Checked for Currency on 08-Mar-2013***
***Checked for Currency on 19-Aug-2014***
ASAP suddenly stops processing work orders and after investigation, it was figured out that Weblogic threads got stuck due to some issue and a few orders were in a 101 state (i.e. "WO Loading state"). After that not a single order was submitted to the SARM.
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