Legacy Knowledge Base
Published Sep. 10, 2025

HotDeployException thrown at startup sometimes for some of our custom portlets

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

  • we have a problem with our portlets. Sometimes when we restart Liferay, some portlets are failing to deploy. We do not have exact scenario. It can happen for any of our portlet during restart.

    Here is exception that we can see in logs:

    com.liferay.portal.kernel.deploy.hot.HotDeployException: Error registering portlets for rss-portlet
        at com.liferay.portal.kernel.deploy.hot.BaseHotDeployListener.throwHotDeployException(BaseHotDeployListener.java:29)
        at com.liferay.portal.deploy.hot.PortletHotDeployListener.invokeDeploy(PortletHotDeployListener.java:91)
        at com.liferay.portal.kernel.deploy.hot.HotDeployUtil._fireDeployEvent(HotDeployUtil.java:167)
        at com.liferay.portal.kernel.deploy.hot.HotDeployUtil.fireDeployEvent(HotDeployUtil.java:68)
    ...

Environment

  • QR

Resolution

  • This probably happens if you have a significant number of war modules (15-20+), and it happens for specifically these kind of modules (war)
  • if that's the case, you might be running into the issue described and fixed by https://liferay.atlassian.net/browse/LPD-29738
  • to resolve it, upgrade to at least a version that includes that fix (2024.Q2.6, 2024.Q3.0) or kindly request a hotfix with this fix

 

Did this article resolve your issue ?

Legacy Knowledge Base