Submit Feedback
Legacy Knowledge Base
Published Sep. 10, 2025

After upgrading from 7.2 to 7.3, Style Books throws IllegalArgumentException

Written By

Sivakumar Perumal

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

  • After upgrading from 7.2 to 7.3, Style Books is inaccessible

  • Steps to Reproduce:
    1. Launch a clean 7.2 DXP bundle
    2. Shut down the bundle once the portal appears in the browser
    3. Upgrade to 7.3 and launch the 7.3 bundle
    4. Navigate to [Site_Administration] > Design > Style Books
  • Actual result: Style Books is unavailable. The message "Style Books is temporarily unavailable." is displayed.
  • Expected result: Style Books is available and does not cause errors.

Environment

  • Liferay DXP 7.3

Resolution

  • The observed behavior is a known issue LPS-127157 and will be fixed in an upcoming Fix Pack.
  • If the hotfix is required for this issue, please create a support ticket requesting hotfix by attaching patch details.
  • There are also two workarounds to fix this issue:
    • The first one is to run the following Groovy script in Server Administration after startup:
      import com.liferay.portal.kernel.service.CompanyLocalServiceUtil;
      import com.liferay.portal.kernel.service.PortletLocalServiceUtil;
      CompanyLocalServiceUtil.forEachCompanyId {
      companyId -> PortletLocalServiceUtil.checkPortlets(companyId) };
    • The second one is setting module.framework.properties.dependency.manager.thread.pool.enabled=false in the portal-ext.properties.
Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?