WebCenter Content: Imaging Server Has Stuck Threads and Error "TCM-00788; ava.net.SocketTimeoutException: Read timed out" Occurs
(Doc ID 2501258.1)
Last updated on SEPTEMBER 28, 2022
Applies to:
Oracle WebCenter Content: Imaging - Version 11.1.1.9.0 to 11.1.1.9.0 [Release 11g]Information in this document applies to any platform.
Symptoms
A large number of stuck threads within Imaging is causing performance issues. Running a search and viewing images in Imaging is very slow.
Thread Dump:
[2018-12-28T17:14:12.824+11:00] [IPM_server1] [NOTIFICATION] [] [oracle.imaging.agents] [tid: [ACTIVE].ExecuteThread: '135' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: <ECID>] [APP: imaging] parsed another document
[2018-12-28T17:14:12.825+11:00] [IPM_server1] [ERROR] [TCM-00156] [oracle.imaging.agents] [tid: [ACTIVE].ExecuteThread: '135' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: <ECID>] [APP: imaging] Error indexing document number 2.[[
oracle.imaging.InputAgentException: TCM-70025: There is no valid document id to run the command on.
faultType: SYSTEM
Stuck Thread:
Line 327: "[STUCK] ExecuteThread: '309' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock java.util.concurrent.locks.ReentrantLock$NonfairSync@712d005c WAITING
Line 495: "[STUCK] ExecuteThread: '305' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock oracle.imaging.session.SessionData@622da9e4 WAITING
Changes
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! |
In this Document
Symptoms |
Changes |
Cause |
Solution |