Order Failed Event Received From ASAP Is Not Handled By OSM, As A Result In-progress Count Grows In OSM
(Doc ID 2096402.1)
Last updated on JANUARY 30, 2024
Applies to:
Oracle Communications ASAP - Version 7.2.0 and laterOracle Communications Order and Service Management - Version 7.2.2 and later
Information in this document applies to any platform.
Symptoms
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
end-tag "".]
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 |