My Oracle Support Banner

Cannot Lookup Automator Errors due to vfs_cache errors (Doc ID 2015046.1)

Last updated on SEPTEMBER 18, 2017

Applies to:

Oracle Communications Order and Service Management - Version 7.2.2 and later
Information in this document applies to any platform.

Symptoms


We are seeing "Cannot create automator errors"  in the  logs. This is blocking messages being consumed by the external automator.

[ERROR] - 2015-02-19 08:28:33 AutomationDispatcher:? - Cannot create automator
javax.naming.NameNotFoundException: While trying to lookup 'automation.plugin/internal/task/CharterNG_SOM_Solution/1.0.0.26.0/SendSodiCheckInToCOMTask/do' didn't find subcontext 'automation'. Resolved ''; remaining name 'automation/plugin/internal/task/CharterNG_SOM_Solution/1/0/0/26/0/SendSodiCheckInToCOMTask/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)

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


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