Failure To Release Outstanding Near Cache Key Lock(s) When Truncate Event Occurs, Resulting in Stuck Threads On Not Released Client Side Key Locks
(Doc ID 3015965.1)
Last updated on APRIL 16, 2024
Applies to:
Oracle Coherence - Version 12.2.1.4.0 and laterInformation in this document applies to any platform.
Symptoms
In a domain WebLogic application clusters are targeted to a Coherence cluster. Intermittently one of the servers experiencing lots of stuck threads as follows. Applications are with a wrapper that does get(key) or getAll(ketset) or put or delete calls. Sometimes they truncate the cache too, from the thread dumps collected at the time of a server apart from the rest of the other servers reports 100's of stuck threads did not give a clue for finding a thread that is a lock holder for an extended of period.
Ex:
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 |
Cause |
Solution |
References |