Orders Failing In Cluster Set Up With Managed Servers
(Doc ID 2261698.1)
Last updated on MARCH 30, 2023
Applies to:
Oracle Communications Order and Service Management - Version 7.3.1.0.0 to 7.3.5.0.0 [Release 7.3.0]Information in this document applies to any platform.
Symptoms
OSM 7.3.1.0.4 version,
Orders failing in Cluster set up with Managed Servers
Customer have a Cluster setup with 3 Managed Servers each for COM and SOM.
COM - 1 Admin Server, 3 Managed Servers
SOM - 1 Admin Server, 3 Managed Servers
The Order Processing fails when all 3 nodes are Up and Running. The order gets stuck and doesn't consume any response.
ERROR
-----------------------
The following is the error message we get with 3 nodes running.
javax.jms.JMSException: Unable to get JNDI name from queue name mslv/oms/oms1/internal/jms/events for server com_ms01
at com.mslv.oms.handler.cluster.ClusterMember.getDestinationJNDIName(ClusterMember.java:197)
at oracle.communications.ordermanagement.cluster.message.impl.RemoteMessageRequestHandlerImpl.getEventQueueJNDI(RemoteMessageRequestHandlerImpl.java:101)
at oracle.communications.ordermanagement.cluster.message.impl.AbstractMessageRequestHandler.redirectMessageToEventQueueIfRequired(AbstractMessageRequestHandler.java:99)
at oracle.communications.ordermanagement.cluster.impl.DefaultBusinessRequestRouterImpl.routeRequest(DefaultBusinessRequestRouterImpl.java:73)
at oracle.communications.ordermanagement.cluster.message.ClusterMessageHandlerBean.onMessage(ClusterMessageHandlerBean.java:99)
at oracle.communications.ordermanagement.security.ControllerBean.processExternalListenerAutomationMessage(ControllerBean.java:650)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
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 |