Enabling OACC In OSM 7.3.0.1.0 In WLS Cluster Caused Error - javax.jms.JMSException: Unable to get JNDI name from queue name mslv/oms/oms1/internal/jms/events
(Doc ID 2188356.1)
Last updated on FEBRUARY 27, 2019
Applies to:
Oracle Communications Order and Service Management - Version 7.3.0.0.0 to 7.3.0.0.0 [Release 7.3.0]Information in this document applies to any platform.
Review relevance Mar 2, 2018
Symptoms
When enabling OACC In OSM 7.3.0.1.0 which installed in Oracle Fusion Middleware 12.1.3 Cluster, the following error was shown in log files
[2016-04-07T05:08:34.151-07:00] [ms2] [ERROR] []
[oracle.communications.ordermanagement.cluster.message.ClusterMessageHandlerBean] [tid:[ACTIVE].ExecuteThread: '9' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <USERNAME>] [ecid: d5d2af48-c5ac-4831-b145-e8e78f00a83f-00001e4d,1:29519]
[APP: oms] Failed to process cluster request for order ID [xxxx][[javax.jms.JMSException: Unable to get JNDI name from queue name
mslv/oms/oms1/internal/jms/events for server ms1
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:150)
at com.mslv.oms.security.base.ControllerBean.processExternalListenerAutomationMessage(ControllerBean.java:1381)
at com.mslv.oms.security.base.OMSController_h9cupp_EOImpl.__WL_invoke(Unknown Source)
at weblogic.ejb.container.internal.SessionRemoteMethodInvoker.invoke(SessionRemoteMethodInvoker.java:34)
at com.mslv.oms.security.base.OMSController_h9cupp_EOImpl.processExternalListenerAutomationMessage(Unknown Source)
at com.mslv.oms.security.base.OMSController_h9cupp_EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:226)
at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:303)
at com.mslv.oms.security.base.OMSController_h9cupp_EOImpl_12130_WLStub.processExternalListenerAutomationMessage(Unknown Source)
at oracle.communications.ordermanagement.automation.plugin.AbstractExternalReceiverDispatcher.processMessage(AbstractExternalReceiverDispatcher.java:148)
at com.mslv.oms.automation.AutomationDispatcher.onLocalMessage(AutomationDispatcher.java:240)
at com.mslv.oms.automation.plugin.AutomationDispatcherImpl$2.routeRequest(AutomationDispatcherImpl.java:138)
at oracle.communications.ordermanagement.cluster.message.ClusterMessageHandlerBean.onMessage(ClusterMessageHandlerBean.java:150)
at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:451)
at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:375)
at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:310)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4855)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:4529)
at weblogic.jms.client.JMSSession.executeMessage(JMSSession.java:3976)
at weblogic.jms.client.JMSSession.access$000(JMSSession.java:120)
at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:5375)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:548)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:311)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:263)
Changes
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 |
| Changes |
| Cause |
| Solution |
| References |