Order Stuck in Failed State Even After Invoking ResolveFailure
(Doc ID 2026134.1)
Last updated on MARCH 15, 2019
Applies to:
Oracle Communications Order and Service Management - Version 7.2.2 to 7.2.4 [Release 7.2]Information in this document applies to any platform.
Symptoms
OSM was not able to resolve the order when multiple threads call the fail order API at the same time (specifically, the failOrderWithInfiniteGracePeriod method).
When this occurs OSM moves the order to Failed state as expected. The problem is when you invoke ResolveFailure but the order remains in Failed state no matter how many times the ResolveFailure is invoked. The order simply gets stuck with status Failed.
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 |
| Cause |
| Solution |
| References |