BCOM CN - JMS Bridges Configured With Started: False Start Anyway
(Doc ID 3069486.1)
Last updated on JANUARY 28, 2025
Applies to:
Oracle Communications Order and Service Management - Version 7.4.1.0.0 and laterInformation in this document applies to any platform.
Symptoms
In a OSM Cloud Native project config file, JMS bridge config has a started: parameter that can be set to true/false.
However, bridges that are configured with started: false are starting anyway and transition to "forwarding messages".
A parameter to disable JMS bridges without removing their configuration completely is required to work
example:
- name: Response_Queue
sourceDestination: Response_Queue_EXTERNAL # should match with one of the destinations configured in the instance spec file
targetDestination: Response_Queue_OSM # should match with one of the destinations configured in the instance spec file
qualityOfService: Exactly-once # Exactly-once Atmost-once Duplicate-okay
started: false # true or false
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 |