Submit Feedback
Legacy Knowledge Base
Published Sep. 10, 2025

Segments API taking more time

Written By

Apsara Raheja

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

  • When there are around 230 user segments, it displays content based on the segment when the user logs in. Since there are more segments, the segment API takes more time to get the user segment.
    long[] segmentsEntryIds = _segmentEntryProviderRegistry.getSegmentsEntryIds(siteGroupId,
    name, userId, context);
    This issue is related to performance issues. API is taking too much time because of this page load time, which has increased to more than 2 minutes.

Environment

  • Liferay DXP 7.2 with fix-pack-20

Resolution

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

Additional Information

  • Upgrade the DXP update to the latest one to achieve the expected behavior: Upgrade Basics
  • All patching-tool commands must be executed from the {liferay_home}/patching-tool directory:​
    For Ubuntu: ./patching-tool.sh 
    For Windows: patching-tool.bat
Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?