My Oracle Support Banner

Adding A Node In OSM Cluster Puts OSM Ear File To Warning State (Doc ID 1904642.1)

Last updated on MARCH 27, 2019

Applies to:

Oracle Communications Order and Service Management - Version 7.2.0 to 7.2.2 [Release 7.2]
Information in this document applies to any platform.


On the OSM 7.2.0 version, in the  BEA WebLogic Server

Adding a node in OSM Cluster Puts  OSM ear file into a warning state

Customer just added a node (osmserver2) into the OSM cluster which already had 2 nodes (osmserver1 and osmserver2) by following the steps mentioned in  .
Note that customer did not create JNDI name for oms_cartridge_deploy_osmserver3 because even existing oms_cartridge_deploy_osmserver1 and oms_cartridge_deploy_osmserver2 also did not have any JNDI names associated with them.

Everything looks ok, and orders are also flowing through, but the OMS.ear goes into a warning state for osmserver3.


Warning message is -

DeployCartridgeMDB (mslv/provisioning/internal/ejb/deployCartridgeQueue) - MDB application oms is NOT connected to messaging system.

osmserver3 logs show -
osmserver3.out00006:The destination for the MDB DeployCartridgeMDB(Application: oms, EJBComponent: cartridgemgmt.jar) could not be resolved at this time. Please ensure the destination is available at the JNDI name mslv/provisioning/internal/ejb/deployCartridgeQueue. The EJB container will periodically attempt to resolve this MDB destination and additional warnings may be issued.>

Customer not able to add 3rd node for testing the process for horizontal scalability.


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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.