Hello!
We're often facing the issue with the threads stuck in our ver. 4.2 D2's Weblogic application server instance eventually bringing the application down over a period of time.
The threads are getting stuck due to services/ resrouces which belong to Documentum D2 having locked like DfCabinet and TopicAspect
Here's what I could find from the thread dump:
"[STUCK] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'" id=16 idx=0x48 tid=7116 prio=1 alive, blocked, native_blocked, daemon
-- Blocked trying to get lock: com/documentum/fc/client/DfCabinet@0x0000000009539A88[lazy unlocked]
"[STUCK] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'" id=22 idx=0x5c tid=7984 prio=1 alive, blocked, native_blocked, daemon
-- Blocked trying to get lock: com/documentum/services/collaboration/impl/TopicAspect@0x000000000A253E30[lazy unlocked]
Could this be due to the Lazy lock option which is enabled by default for JRockit JVM ? as mentioned in this article:
Understanding Threads and Locks
Please let me know if someone has faced such issue and any resolution would be of great help.
Thank you!
