JMSOrderException Appears in Operations Mobile App (OMA) Managed Server (Doc ID 2898685.1)

Last updated on OCTOBER 10, 2022

Applies to:

Oracle Utilities Network Management System - Version 2.5.0.1.0 to 2.6.0.0.0 [Release 2.5 to 2.6]
Oracle Network Management for Utilities - DMS - Version 2.5.0.1.0 to 2.6.0.0.0 [Release 2.5 to 2.6]
Information in this document applies to any platform.

Symptoms

On : 2.5.0.2.0 version, Installation

When running in a clustered environment, Operations Mobile App (OMA) fails to connect with NMS .

These errors appear in the OMA managed server log:

<Warning> <JMS> <BEA-040442> <While attempting to bind JNDI name jms/scada-analog-queue for destination SystemModule-scadaserver2!scada-analog-queueserver2 in module null, a JNDI name conflict was found. This destination has not been bound into JNDI.>
<Warning> <JMS> <BEA-040442> <While attempting to bind JNDI name jms/scada-digital-queue for destination SystemModule-scadaserver2!scada-digital-queueserver2 in module null, a JNDI name conflict was found. This destination has not been bound into JNDI.>
<Warning> <JMS> <BEA-040442> <While attempting to bind JNDI name jms/scada-status-queue for destination SystemModule-scadaserver2!scada-status-queueserver2 in module null, a JNDI name conflict was found. This destination has not been bound into JNDI.>

WARN publish.FlexPublisherBean: weblogic.jms.extensions.JMSOrderException: [JMSExceptions:045119]The current JMS message is a Unit-of-Order (UOO) or Unit-of-Work (UOW) message that cannot be sent to the distributed destination (DD) "SystemModule-omaserver1!nms-to-omaserver1". This DD has its UnitOfOrderRouting attribute configured to "Hash", which does not support UOO/UOW messages when either a DD is configured in a Resource Group scope, or a DD is hosted on a JMS server that is targeted to a cluster. To fix this issue: change the UnitOfOrderRouting attribute to "PathService" and ensure a Path Service is configured and running in the current scope.
weblogic.jms.extensions.JMSOrderException: [JMSExceptions:045119]The current JMS message is a Unit-of-Order (UOO) or Unit-of-Work (UOW) message that cannot be sent to the distributed destination (DD) "SystemModule-omaserver1!nms-to-omaserver1". This DD has its UnitOfOrderRouting attribute configured to "Hash", which does not support UOO/UOW messages when either a DD is configured in a Resource Group scope, or a DD is hosted on a JMS server that is targeted to a cluster. To fix this issue: change the UnitOfOrderRouting attribute to "PathService" and ensure a Path Service is configured and running in the current scope.