Document ID: TEC596547
Last Modified Date: 8/1/2013
Authored By: Mary_Clark
- CA Application Performance Management
Agent Version: 8.2.3
Tomcat Version: 6.0
There is a known Liferay issue that causes a JVM hang. It may appear that the APM Java Agent is the cause, but thread dumps clearly indicate that APM is not the culprit.
The following entry may appear in the thread dump and the log:
6:07:32,345 WARN [ThreadPoolAsynchronousRunner:608] com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@735904ac -- APPARENT DEADLOCK!!! Creating emergency threads for unassigned pending tasks!
This is a known Liferay issue.
Some workarounds for this issue are suggested in online forums. In some cases the problem can be worked around by increasing the max pool size.