Order Stuck in Failed State Even After Invoking ResolveFailure
Last updated on JUNE 07, 2016
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.
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.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms