Submit Feedback
Legacy Knowledge Base
Published Sep. 10, 2025

Thread deadlock during startup of liferay in cluster

Written By

Sorin Pop

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.

Issue

  • I'm not 100% sure on how to reproduce/trigger it, but it seems that when there is active traffic to the cluster, there is a fair chance that one of the nodes will deadlock during startup of the portal. We see this happen almost every deployment on production, however on dev, test & acc it almost never happens (probably because these have much less traffic during the deployments).

  • Today however I did manage to reproduce it sometimes on our dev servers, using our smoketest to put some traffic on the system, and then restarting one of the nodes in the cluster.

    The result is that the startup hangs around the time where it tries to load the company configurations...

    Company properties can be overwrritten by setting the environment variable LIFERAY_PROPS_BY_COMPANY_3145002
    Loading file:/home/liferay/liferay-dxp-2024.q3.13/portal-ext.properties for company ID 3145002 and web ID msus
    Company properties can be overwrritten by setting the environment variable LIFERAY_PROPS_BY_COMPANY_3145002
    Loading jar:file:/home/liferay/liferay-dxp-2024.q3.13/tomcat/webapps/ROOT/WEB-INF/shielded-container-lib/portal-impl.jar!/portal-developer.properties for company ID 3145002 and web ID msus
    Company properties can be overwrritten by setting the environment variable LIFERAY_PROPS_BY_COMPANY_3145002

  • Then nothing after this (we have 10 companies); a restart can fix it, but may simply give the same issue (on production the solution is generally to restart both nodes at the same time, which is annoying because it gives outage that we try to prevent by having the cluster in the first place).

Environment

  • 2024.q3.13

Resolution

 

Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?