Submit Feedback
Legacy Knowledge Base
Published Sep. 10, 2025

No theme found During Startup When a Theme is Not Yet Deployed

Written By

Daniel Martinez Cisneros

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

  • The server logs show the following messages before the theme is fully deployed:
2025-07-09 06:25:20.463 WARN  [https-jsse-nio-8443-exec-14][ThemeLocalServiceImpl:220] No theme found for specified theme id classic_WAR_classictheme. Returning the default theme.
  • This issue happens when an HTTP request (e.g., from a health check or a browser request) reaches the server before essential themes like classic-theme or custom theme are fully deployed. The system cannot find the required theme, which results in an error.

Environment

  • Liferay DXP 2024.Q1

Resolution

This behavior is expected when Liferay receives requests before its startup process is complete. To prevent these errors, it is recommended to manage incoming traffic during the startup phase.

  • Place a load balancer or a reverse proxy in front of the Liferay instance.
  • Configure the proxy to display a temporary maintenance page.
  • Keep the maintenance page active until the Liferay instance has fully started and is ready to serve requests.
  • Once Liferay is fully initialized, switch the proxy to direct traffic to the Liferay instance.

This approach ensures that no requests hit the Liferay server while it is still deploying core components, thus avoiding errors caused by race conditions during startup.

 

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