OSM Response Messages Are Not Getting Correlated
(Doc ID 2807452.1)
Last updated on APRIL 15, 2024
Applies to:
Oracle Communications Order and Service Management - Version 7.4.1.0.0 and laterInformation in this document applies to any platform.
Symptoms
On : 7.4.1.0.0 version, Other
OSM COM and SOM order tasks couldn't correlate the message from the downstream systems even when the messages are posted to OSM response queue with correct correlation id/ message property/ message body.
Below are the steps followed to ensure the issue. Below is the error message.
ERROR
-----------------------
Please ignore javax.naming.NameNotFoundException: While trying to lookup 'zyz.xyz.xyz' error in logs.
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Submitted COM order, SOM order created internally and when SOM updates (Milestones) are sent to COM the messages are not consumed
2. Submitted COM order, SOM order created internally and when SOM updates ("COMPLETE" response after SOM completion) are sent to COM the message was not consumed
3. Submitted COM order, SOM order created internally and request was sent to UIM but the response was not consumed.
Changes
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 |
| Changes |
| Cause |
| Solution |
| References |