This discussion is archived
1 Reply Latest reply: Nov 2, 2012 1:17 PM by user491422 - oracle RSS

Cannot create automator Custom Automation Plugin

Lucas Andres Muñoz Newbie
Currently Being Moderated
Hi all,

I have a little problem with Customs Automation Plugins, I work with a group of OSM developers, we use the same installation of OSM and even the same reference of Notebook, but when we develop a Custom Automation Plugin (Java Class that connects to a database and extract some information to make an Order Data Update), my teams mates OSM instances work correctly but mine generate an error and always is the same for different Customs Automatios Plugins.

I have been looking for this Error on Oracle Support and I already find this:
It seems that is my error, but is strange because of my team’s mates OSM instances like I said before.

This is the error:

<Error> <oms> <CO-L-14109ZG> <AdminServer> <ExecuteThread: '13' for queue: 'oms.automation'> <oms-automation> <BEA1-43AD8411EF12560E5D6A> <46645d5ea9e48215:5aa9f334:13ab1fa4b23:-8000-0000000000000374> <1351607306050> <BEA-000000> <automation.AutomationDispatcher: Cannot create automator
javax.naming.NameNotFoundException: While trying to lookup 'automation.plugin/internal/task/NcaOsmOrquestacionBA_TOIP/' didn't find subcontext 'automation'. Resolved ''; remaining name 'automation/plugin/internal/task/NcaOsmOrquestacionBA_TOIP/1/0/0/0/0/TANotificarCrmEstadosBA_TOIP/do'
     at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(
     at weblogic.jndi.internal.BasicNamingNode.lookupHere(
     at weblogic.jndi.internal.ServerNamingNode.lookupHere(
     at weblogic.jndi.internal.BasicNamingNode.lookup(
     at weblogic.jndi.internal.BasicNamingNode.lookup(
     at weblogic.jndi.internal.WLEventContextImpl.lookup(
     at weblogic.jndi.internal.WLContextImpl.lookup(
     at javax.naming.InitialContext.lookup(
     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(
     at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(
     at weblogic.ejb.container.internal.MDListener.onMessage(
     at weblogic.jms.client.JMSSession.onMessage(
     at weblogic.jms.client.JMSSession.execute(
     at weblogic.jms.client.JMSSession.executeMessage(
     at weblogic.jms.client.JMSSession.access$000(
     at weblogic.jms.client.JMSSession$
     at weblogic.kernel.ExecuteThread.execute(
  • 1. Re: Cannot create automator Custom Automation Plugin
    user491422 - oracle Journeyer
    Currently Being Moderated
    To prevent the error from happening infinitely, set JMS redelivery settings on all OSM queues to a reasonable value (for development this is typically 1 redelivery attempt max with 5000ms between attempts, for production these values are usually higher at 15-20 attempts with 7000-15000ms between attempts).

    As for why it can't find the plugin, it looks like a deployment problem with the plugin ear file. I would suggest comparing your list of deployments with your colleagues in the wls console.



  • Correct Answers - 10 points
  • Helpful Answers - 5 points