TEC596547: Known Liferay Issue causes JVM hang in Tomcat, APPARENT DEADLOCK

Document created by Mary_Clark Employee on May 26, 2016Last modified by J.J. Lovett on May 26, 2016
Version 2Show Document
  • View in full screen mode

Document ID:  TEC596547

Last Modified Date:  8/1/2013
Authored By: Mary_Clark

  • Products
    • CA Application Performance Management
  • Components
    • INTROSCOPE

Description:

Environment details:

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!

Solution:

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.

http://www.liferay.com/community/forums/-/message_boards/message/5645944

http://issues.liferay.com/browse/LPS-11779

http://stackoverflow.com/questions/475893/which-are-the-required-c3p0-settings-for-hibernate-in-order-to-avoid-deadlocks

 

Search the Entire CA APM Knowledge Base

 

search-kb.jpg

Attachments

    Outcomes