Order Failed Event Received From ASAP Is Not Handled By OSM, As A Result In-progress Count Grows In OSM
Last updated on JANUARY 18, 2016
Applies to:Oracle Communications ASAP - Version 7.2.0 and later
Information in this document applies to any platform.
60% of orders are failing with the following exception in ASAP. Orders remain in a Failed state in ASAP, but the responses are not reaching OSM. OSM in-progress order count is growing.
FAIL:javax.xml.bind.UnmarshalException - with linked
exception: [org.xml.sax.SAXParseException: The element type
"DeviceFilter" must be terminated by the matching
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