Legacy Knowledge Base
Published Sep. 10, 2025

Performance Issue for Thread Counts While Processing JSP files

Written By

Justin Choi

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.

This article is designed to help administrators tune performance in Liferay DXP 7.0 when the active thread count approaches the maximum allowed thread count.

The reason for this performance issue is because the values for the properties layout.prototype.merge.lock.max.time and layout.set.prototype.merge.lock.max.time are being handled as milliseconds rather than seconds. This means that if a site template merge were to take longer than half a second, and many people are visiting the same site, a deadlock will occur.

In addition, administrators may encounter some threads being blocked while processing JSP files.

Resolution

A temporary solution is to set the portal properties to 1000 times larger than their default values.

	#layout.prototype.merge.lock.max.time=300
	layout.prototype.merge.lock.max.time=300000

	#layout.set.prototype.merge.lock.max.time=600
	layout.set.prototype.merge.lock.max.time=600000
	

Additional Information

See LPS-76668 for more information and a possible resolution of the issue.

Did this article resolve your issue ?

Legacy Knowledge Base