Content Server Fails to Start Due to CoreWebdav Exception (Doc ID 1369032.1)

Last updated on JULY 26, 2017

Applies to:

Oracle Universal Content Management - Version: 10.1.3.3.1 to 10.1.3.3.4 - Release: 10gR3 to 10gR3
Information in this document applies to any platform.

Symptoms

The Content Server fails to start. The Content Server log shows an exception like the following:

'CoreWebdav' component, version '2009_06_17 (build 30) br-10g-10.1.3.5-release', extends webdav:2.0-2.0 feature(s)
Failed to initialize the server.
(internal) 10.19 13:42:29.092 main !csFailedToInitServer (!syServiceRuntime,java.lang.NullPointerException
at webdavcomponent.WebdavLocksManager.loadLocks(WebdavLocksManager.java:449)
at webdavcomponent.WebdavFilters.doFilter(WebdavFilters.java:124)
at intradoc.shared.PluginFilters.filter(PluginFilters.java:94)
at intradoc.server.IdcExtendedLoader.executeFilter(IdcExtendedLoader.java:287)
at intradoc.server.IdcExtendedLoader.extraBeforeCacheLoadInit(IdcExtendedLoader.java:257)
at intradoc.server.IdcSystemLoader.loadCaches(IdcSystemLoader.java:928)
at intradoc.server.IdcServerManager.init(IdcServerManager.java:81)
at IdcServer.init(IdcServer.java:64)
at IdcServer.main(IdcServer.java:37)
)-exception stack


If the CoreWebdav component is disabled, then the Content Server will start with no issue.

Cause

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