Legacy Knowledge Base
Published Jul. 2, 2025

Custom context path is not working

Written By

Pooja Bhambani

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 changing, the root context path to custom context the commerce components and system settings taking more time to load.
  • Steps to reproduce:
    1. Start Liferay with Commerce installed.
    2. Change the ROOT folder name (under{LIFERAY_HOME}/tomcat-9.0.37/webapps/ROOT) to 'myportal'.
    3. Change the ROOT.xml file name (under {LIFERAY_HOME}/tomcat-9.0.37/conf/Catalina/localhost/) to 'myportal.xml'.
    4. Clear temp and work directories under TOMCAT_HOME.
    5. Restart the server.
    6. Hit this URL "localhost:8080/myportal/"

    Expected Result:  System settings and commerce products should take less time to load.
    Actual Result: System settings and commerce products are taking more time to load.

Environment

  • Liferay DXP 7.3
  • Commerce 3.0

Resolution

  • The observed behavior is a known issue/bug.
  • If the hotfix is required for this issue, please create a support ticket requesting hotfix by attaching patch details.
  • Installing Fix Packs and Hotfixes on Liferay DXP will guide to install this hotfix in the respective environment.

Additional Information

Did this article resolve your issue ?

Legacy Knowledge Base