My Oracle Support Banner

Frequent Stuck Threads In Imaging (Doc ID 2697825.1)

Last updated on SEPTEMBER 26, 2023

Applies to:

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

Symptoms

Stuck threads in WebCenter Content: Imaging with the below error in server log files:

<Error> <WebLogicServer> <BEA-000337> <[STUCK] ExecuteThread: '31' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "634" seconds working on the request "Http Request Information: weblogic.servlet.internal.ServletRequestImpl@128f8d65[GET /imaging/renderimage/renderimage/ZEROdeg/fitFITSCALE/100pct/annotationsfalse/page1/version1/11.IPM_1234567.JPG]
", which is more than the configured time (StuckThreadMaxTime) of "600" seconds in "server-failure-trigger". Stack trace:
java.lang.Thread.sleep(Native Method)
oracle.imaging.viewer.cache.manager.CacheManagerBean.locateObjectPageInCache(CacheManagerBean.java:248)
<stack trace continues>

Also see the following errors:

<Warning> <EJB> <[ACTIVE] ExecuteThread: '33' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <[severity-value: 16] [rid: <RID>3] [partition-id: 0] [partition-name: DOMAIN] > <BEA-010065> <MessageDrivenBean threw an Exception in onMessage(). The exception is:
javax.ejb.EJBException: Object is currently being processed..

 

Changes

Trying to render corrupted documents, or documents that OIT cannot process.

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!


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