ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Known Liferay Issue causes JVM hang in Tomcat, APPARENT DEADLOCK

book

Article ID: 48589

calendar_today

Updated On:

Products

CA Application Performance Management Agent (APM / Wily / Introscope) INTROSCOPE

Issue/Introduction

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[email protected]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

Environment

Release:
Component: APMISP