OSM Automation Is Not Picking JMS Messages From External Systems. Messages In Queue is In Delayed State
(Doc ID 1551053.1)
Last updated on MARCH 29, 2023
Applies to:
Oracle Communications Order and Service Management - Version 7.0.3 and laterOracle Communications Design Studio - Version 3.1.4 and later
Information in this document applies to any platform.
******Currency checked on 22-Sep-2017*********
Goal
OSM automation is unable to pickup messages from the JMS Queue. Messages are displayed in the console in a delayed state. When we are restarting the server, automation is picking up the same message and processing. The problem is happening across both managed servers in the environment.
Observed the following error in the OSM logs:
Design studio and OSM version:
DS 3.1.1
OSM version is 7.0.3 Patchset 18.
In Design studio 3.1.1 there is no option for "Optimized" selection and also the highest build that can be set as target version is 7.0.1 (cannot set it to 7.0.3).
Solution
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
| Goal |
| Solution |
| References |