Error " <Vuelink:ERROR> Failed to verify or update null" in Tomcat stdout Log

(Doc ID 1911234.1)

Last updated on JULY 13, 2017

Applies to:

Oracle Autovue for Agile Product Lifecycle Management - Version 20.2.0 and later
Information in this document applies to any platform.


The customer is using AutoVue 20.2.2 from Agile 9.3.3. Any type of files that Autovue picks up generates this error message in Tomcat stdout log file:

2014-05-02 18:01:19 Commons Daemon procrun stdout initialized                                                                                                                                                                                                                                               *******************************************                                                                                                                                                                                                                                                                                                                    File Manager Initialized Successfully...                                                                                                                                                                                                                                                                                               *******************************************                                                                                                                                                                                                                                                                                                                   Fri May 02 18:01:34 PDT 2014 Creating


 Fri May 02 18:01:34 PDT 2014 Initializing VueBean Pool ...

Fri May 02 18:01:34 PDT 2014 Loading cookies ...

Fri May 02 18:01:34 PDT 2014 Creating JobGroup ...

<2014-05-02 18:01:54,549> <Vuelink:ERROR> Failed to verify or update null


   at java.util.Hashtable.put(     

   at com.cimmetry.vuelink.context.GenericContext.setInitParameter(Unknown Source)     

   at com.cimmetry.vuelink.Vuelink.registerDMSContext(Unknown Source)     

   at com.cimmetry.vuelink.Vuelink.init(Unknown Source)     

   at com.agile.autovueconnector.DMS.init(     

   at javax.servlet.GenericServlet.init(     

   at org.apache.catalina.core.StandardWrapper.initServlet(     

   at org.apache.catalina.core.StandardWrapper.loadServlet(     

   at org.apache.catalina.core.StandardWrapper.allocate(     

   at org.apache.catalina.core.StandardWrapperValve.invoke(     

   at org.apache.catalina.core.StandardContextValve.invoke(     

   at org.apache.catalina.authenticator.AuthenticatorBase.invoke(     

   at org.apache.catalina.core.StandardHostValve.invoke(     

   at org.apache.catalina.valves.ErrorReportValve.invoke(     

   at org.apache.catalina.valves.AccessLogValve.invoke(     

   at org.apache.catalina.core.StandardEngineValve.invoke(       

   at org.apache.catalina.connector.CoyoteAdapter.service(     

   at org.apache.coyote.http11.Abs



The error message is written to the log file only the first time AutoVue is run.  No matter how many files of different types are viewed, the error message only appears in the log file once. AutoVue always works fine. However, the error message doesn't seem to be reporting on anything that actually matters.  




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