Access To The WCC May Be Slow Or Timeout Due To User Cache Resizing

(Doc ID 2137795.1)

Last updated on FEBRUARY 01, 2018

Applies to:

Oracle WebCenter Content - Version and later
Information in this document applies to any platform.


When accessing the WebCenter Content server, it may take a long time to complete or fail.

This can occur when initially logging into the WCC or when performing actions within the WCC.

There can be several causes for this kind of issue; this KM will focus on one particular cause.

The WCC managed server log will show an exception as like:

<Apr 27, 2016 11:17:57 AM CDT> <Error> <WebLogicServer> <BEA-000337> <[STUCK] ExecuteThread: '380' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "683" seconds working on the request "Workmanager: default, Version: 1, Scheduled=true, Started=true, Started time: 683330 ms

POST /cs/idcplg HTTP/1.1



]", which is more than the configured time (StuckThreadMaxTime) of "600" seconds.


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