Com.mslv.oms.automation.AutomationException: Java.lang.RuntimeException: Cannot Lookup Automator (Doc ID 1561347.1)

Last updated on SEPTEMBER 01, 2016

Applies to:

Oracle Communications Order and Service Management - Version 7.2.0 and later
Information in this document applies to any platform.
Checked currency on 05-Jan-2015

Checked currency on 01-Sep-2016

Goal

When orders are fired for a customized cartridge, we are receiving the following exception in the logs. The cartridge has an Automated Task named Install Order Task. Two queries are currently part of the task.

Is there any solution/workaround for this problem?

(1) InstallOrderTask_do.xquery - Automation Type = Xquery Sender
- Event Type = Internal
- Script = Bundle in
(2) InstallOrderTask_Response.xquery - Automation Type = Xquery Automator
- Event Type = External
- Script = Bundle in

<ExecuteThread: '12' for queue: 'oms.automation'>
javax.naming.NameNotFoundException: While trying to lookup 'automation.plugin/internal/task/OracleComms_OSM_O2A_COMSOM_SimpleSolution/1.0.0.0.0/InstallOrderTask/do' didn't find subcontext 'automation'. Resolved ''; remaining name 'automation/plugin/internal/task/OracleComms_OSM_O2A_COMSOM_SimpleSolution/1/0/0/0/0/InstallOrderTask/do'
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:247)
at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:411)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at com.mslv.oms.automation.AutomationDispatcher.i(Unknown Source)
at com.mslv.oms.automation.AutomationDispatcher.h(Unknown Source)
at com.mslv.oms.automation.AutomationDispatcher.c(Unknown Source)
at com.mslv.oms.automation.plugin.AutomationEventHandlerImpl.c(Unknown Source)
at com.mslv.oms.automation.AutomationDispatcher.d(Unknown Source)
at com.mslv.oms.automation.AutomationDispatcher.a(Unknown Source)
at com.mslv.oms.automation.plugin.AutomationEventHandlerImpl.a(Unknown Source)
at com.mslv.oms.automation.plugin.AutomationEventHandlerImpl.c(Unknown Source)
at com.mslv.oms.automation.plugin.AutomationEventHandlerImpl.processMessage(Unknown Source)
at com.mslv.oms.automation.AutomationDispatcher.onLocalMessage(Unknown Source)
at oracle.communications.ordermanagement.cluster.message.e.a(Unknown Source)
at oracle.communications.ordermanagement.cluster.message.impl.c.a(Unknown Source)
at oracle.communications.ordermanagement.cluster.message.impl.c.a(Unknown Source)
at oracle.communications.ordermanagement.cluster.impl.a.a(Unknown Source)
at oracle.communications.ordermanagement.cluster.message.ClusterMessageHandlerBean.onMessage(Unknown Source)
at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:574)
at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:477)
at weblogic.ejb.container.internal.NewJMSMessagePoller.processOneMessage(NewJMSMessagePoller.java:286)
at weblogic.ejb.container.internal.NewJMSMessagePoller.run(NewJMSMessagePoller.java:120)
at weblogic.ejb.container.internal.NewJMSMessagePoller.timerExpired(NewJMSMessagePoller.java:235)
at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
at weblogic.work.ExecuteRequestAdapter.execute(ExecuteRequestAdapter.java:21)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)

 
 

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms