Submit Feedback
Legacy Knowledge Base
Published Sep. 10, 2025

LPKG Index Validation takes too long and ends up in out of memory error

Written By

Adam Zsolnay

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 we start our test server with -Xmx1024Mb after applying a new patch, the LPKG Index Validator is running too long and we are getting GC overhead exception, ending up in OutOfMemoryError:
  • WARN [HikariPool-1 housekeeper][HikariPool:676] HikariPool-1 - Thread starvation or clock leap detected (housekeeper delta=1m36s726ms671µs500ns).
    Exception in thread "NioBlockingSelector.BlockPoller-2" java.lang.OutOfMemoryError: Java heap space
  • For us, it is not possible to disable the Validator in Production.

Environment

  • DXP 7.0

Resolution

  • Increase the maximum heap size to at least 3GB ( -Xmx3g) and restart the server
  • Once it resolved the matter with 3Gb, you can fine-tune the JVM further.

 

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