'Apparent Deadlock' Errors Occurring in Threadpoolworker
(Doc ID 1163103.1)
Last updated on MARCH 12, 2019
Applies to:
Oracle Utilities Framework - Version 2.2.0.0.0 to 2.2.0.0.0 [Release 2.2]Information in this document applies to any platform.
Symptoms
After threadpoolworkers are left running for several days, errors similar to the following start occurring in the threadpoolworker log:
- 2010-07-02 00:31:33,601 [Timer-1] WARN (v2.async.ThreadPoolAsynchronousRunner) com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@17001700 -- APPARENT DEADLOCK!!! Creating emergency threads for unassigned pending tasks!
- 2010-07-02 00:31:33,723 [Timer-1] WARN (v2.async.ThreadPoolAsynchronousRunner) com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@17001700 -- APPARENT DEADLOCK!!! Complete Status:
- 2010-07-02 00:31:33,723 [Timer-1] WARN (v2.async.ThreadPoolAsynchronousRunner) com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@17001700 -- APPARENT DEADLOCK!!! Complete Status:
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 |