Submit Feedback
Legacy Knowledge Base
Published Sep. 10, 2025

java.lang.RuntimeException: com.liferay.portal.lpkg.deployer.LPKGVerifyException: LPKG validation failed

Written By

Thanga Meena

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

  • Why "LPKGVerify RuntimeException" triggers? 
SEVERE: Exception sending context initialized event to listener instance of class com.liferay.portal.spring.context.PortalContextLoaderListener
java.lang.RuntimeException: com.liferay.portal.lpkg.deployer.LPKGVerifyException: LPKG validation failed with 

{[missing requirement com.liferay.alloy.mvc; version=2.3.11; type=osgi.bundle [caused by: Unable to resolve com.liferay.alloy.mvc version=2.3.11: 

missing requirement &(osgi.ee=JavaSE)(version=1.8)]], [missing requirement com.liferay.analytics.message.sender.api; version=1.5.0; type=osgi.bundle [caused by: Unable to resolve com.liferay.analytics.message.sender.api version=1.5.0: missing requirement com.liferay.analytics.message.storage.service; version=[1.0.0,2.0.0) [caused by: Unable to resolve com.liferay.analytics.message.storage.api version=1.0.7: missing requirement &(osgi.ee=JavaSE)(version=1.8)]]], [missing requirement com.liferay.analytics.message.sender.impl; version=1.0.16; type=osgi.bundle [caused by: Unable to resolve com.liferay.analytics.message.sender.impl version=1.0.16: missing requirement com.liferay.analytics.message.sender.constants; version=1.0.0 [caused by: Unable to resolve com.liferay.analytics.message.sender.api version=1.5.0: missing requirement com.liferay.analytics.message.storage.service; version=[1.0.0,2.0.0) [caused by: Unable to resolve com.liferay.analytics.message.storage.api version=1.0.7: missing requirement &(osgi.ee=JavaSE)(version=1.8)]]]], [missing requirement com.liferay.analytics.message.storage.api; version=1.0.7; type=osgi.bundle [caused by: Unable to resolve com.liferay.analytics.message.storage.api version=1.0.7: missing requirement &(osgi.ee=JavaSE)(version=1.8)]], [missing requirement com.liferay.analytics.message.storage.service; version=1.0.18; type=osgi.bundle [caused by: Unable to resolve com.liferay.analytics.message.storage.service version=1.0.18: missing requirement com.liferay.analytics.message.storage.model; version=1.0.0 [caused by: Unable to resolve com.liferay.analytics.message.storage.api version=1.0.7: missing requirement &(osgi.ee=JavaSE)(version=1.8)]]], [missing requirement com.liferay.analytics.settings.api; version=1.3.0; type=osgi.bundle [caused by: Unable to resolve com.liferay.analytics.settings.api version=1.3.0: missing requirement &(osgi.ee=JavaSE)(version=1.8)]], [missing requirement com.liferay.analytics.settings.impl; version=1.0.16; type=osgi.bundle [caused by: Unable to resolve com.liferay.analytics.settings.impl version=1.0.16: missing requirement com.liferay.analytics.message.sender.constants; version=[1.0.0,2.0.0) [caused by: Unable to resolve com.liferay.analytics.message.sender.api version=1.5.0: missing requirement com.liferay.analytics.message.storage.service; version=[1.0.0,2.0.0) [caused by: Unable to resolve com.liferay.analytics.message.storage.api version=1.0.7: missing requirement &(osgi.ee=JavaSE)(version=1.8)]]]], [missing requirement com.liferay.analytics.settings.web; version=1.0.50; type=osgi.bundle [caused by: Unable to resolve com.liferay.analytics.settings.web version=1.0.50: missing requirement com.liferay.portal.configuration.metatype.annotations; version=[1.0.0,2.0.0) [caused by: Unable to resolve com.liferay.portal.configuration.metatype version=2.0.21: missing requirement &(osgi.ee=JavaSE)(version=1.8)]]], [missing requirement com.liferay.announcements.api; version=1.0.2; type=osgi.bundle [caused by: Unable to resolve com.liferay.announcements.api version=1.0.2: missing requirement &(osgi.ee=JavaSE)(version=1.8)]], [missing requirement com.liferay.announcements.uad; version=2.0.12; type=osgi.bundle [caused by: Unable to resolve com.liferay.announcements.uad version=2.0.12: missing requirement com.liferay.user.associated.data.display; version=1.0.0 [caused by: Unable to resolve com.liferay.user.associated.data.api version=2.0.7: missing requirement &(osgi.ee=JavaSE)(version=1.8)]]], [missing requirement com.liferay.announcements.web; version=2.0.52; type=osgi.bundle [caused by: Unable to resolve com.liferay.announcements.web version=2.0.52: missing requirement com.liferay.portal.configuration.metatype.util; version=1.0.0 [caused by: Unable to resolve com.liferay.portal.configuration.metatype version=2.0.21: missing requirement &(osgi.ee=JavaSE)(version=1.8)]]], [missing requirement com.liferay.antivirus.clamd.scanner; version=1.0.10; type=osgi.bundle [caused by: Unable to resolve com.liferay.antivirus.clamd.scanner version=1.0.10: missing requirement com.liferay.portal.configuration.metatype.bnd.util; version=2.0.0 [caused by: Unable to resolve com.liferay.portal.configuration.metatype version=2.0.21: missing requirement &(osgi.ee=JavaSE)(version=1.8)]]], [missing requirement com.liferay.application.list.api; version=2.2.15; type=osgi.bundle [caused by: Unable to resolve com.liferay.application.list.api version=2.2.15: missing requirement &(osgi.extender=osgi.component)(version=[1.3.0,2.0.0)) [caused by: Unable to resolve org.apache.felix.scr version=2.0.6.LIFERAY-PATCHED-5: missing requirement &(osgi.ee=JavaSE)(version=1.8)]]], [missing requirement com.liferay.application.list.my.account.permissions; version=1.0.7; type=osgi.bundle [caused by: Unable to resolve com.liferay.application.list.my.account.permissions version=1.0.7: missing requirement com.liferay.application.list.display.context.logic; version=[1.1.0,2.0.0) [caused by: Unable to resolve com.liferay.application.list.api version=2.2.15: missing requirement &(osgi.extender=osgi.component)(version=[1.3.0,2.0.0)) [caused by: Unable to resolve org.apache.felix.scr version=2.0.6.LIFERAY-PATCHED-5: missing requirement &(osgi.ee=JavaSE)(version=1.8)]]]], [missing requirement com.liferay.application.list.taglib; version=2.0.24; type=osgi.bundle [caused by: Unable to resolve com.liferay.application.list.taglib version=2.0.24: missing requirement com.liferay.application.list.display.context.logic; version=[1.1.0,2.0.0) [caused by: Unable to resolve com.liferay.application.list.api version=2.2.15: missing requirement &(osgi.extender=osgi.component)(version=[1.3.0,2.0.0)) [caused by: Unable to resolve org.apache.felix.scr version=2.0.6.LIFERAY-PATCHED-5: missing requirement &(osgi.ee=JavaSE)(version=1.8)]]]], [missing requirement com.liferay.application.list.user.personal.site.permissions; version=2.0.13; type=osgi.bundle [caused by: Unable to resolve com.liferay.application.list.user.personal.site.permissions version=2.0.13: missing requirement com.liferay.application.list.display.context.logic; version=[1.1.0,2.0.0) [caused by: Unable to resolve com.liferay.application.list.api version=2.2.15: missing requirement &(osgi.extender=osgi.component)(version=[1.3.0,2.0.0)) [caused by: Unable to resolve org.apache.felix.scr version=2.0.6.LIFERAY-PATCHED-5: missing requirement &(osgi.ee=Java
more..................

Environment

  • Liferay DXP 7.0

Resolution

  • Let me explain the different possible ways how it may trigger. The LPKG Index validator is an internal security mechanism. This is how it is designed to ensure that the deployed LPKG files have not been tampered with. It will set off if there are any changes to the deployments.
  • For example: if there is any modification in the LPKG or removed a few LPKG files then this error usually triggers.
  • Hence configure the below property as a workaround for testing purposes in the lowered testing or non-production environment.
    module.framework.properties.lpkg.index.validator.enabled=false 
    // Add this property in the portal-ext.properties and restart the server by deleting the temp directories.

Additional Information

  • The community blog post describing the above property.

    NOTE: Please note that Community resources are written by community members for community members, and therefore not officially sanctioned by Liferay Support like our Help Center Knowledge Base documentation, but they can provide useful information.

 

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