Last updated on NOVEMBER 03, 2016
Applies to:Oracle WebCenter Content - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
With the coded timeout being an estimate as to how long WCC should wait for other cluster nodes' schema publishing and web publishing to complete, remote filesystem speed, remote filesystem access time (may include network speed), number of cluster nodes, and the amount of your custom schema data all effect how long each cluster node may need to wait to publish schema and static and dynamic weblayout files and not lock-out other nodes before their timeout is reached.
Possible to get this error: "javax.servlet.ServletException: Could not start up IDC server deployment" when the timeout is reached.
How to monitor and proactively set that timeout, so the error does not occur?
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