Legacy Knowledge Base
Published Sep. 10, 2025

Upgrading From Fix Pack 8 to 11 Failed Due To NPE

Written By

Laura Li

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 fix pack 8 to 11, the portal starts up with NPE.
    2022-01-06 12:42:49.469 ERROR [default task-1][MainServlet:1168] com.liferay.portal.kernel.events.ActionException: java.lang.NullPointerException
    ......
    Caused by: java.lang.NullPointerException
      at com.liferay.staging.security.internal.permission.StagingPermissionChecker.hasPermission(StagingPermissionChecker.java:128)
      ......
  • Running upgrade:check command in Gogo Shell, it returns the message:
    There is an upgrade process available for com.liferay.dynamic.data.mapping.service
    from 3.2.7 to 3.2.8
  • Running upgrade:execute com.liferay.dynamic.data.mapping.service command in Gogo Shell, OOM may throw out or it stuck at the following message:
    2022-01-11 10:10:23.245 INFO [pipe-upgrade:execute com.liferay.dynamic.data.mapping.service][UpgradeProcess:93] 
    Upgrading com.liferay.dynamic.data.mapping.internal.upgrade.v3_2_8.UpgradeDDMFormDocumentLibraryFields

Environment

  • Liferay DXP 7.2

Resolution

  • The fix LPS-130556 can resolve the issue

 

 

Did this article resolve your issue ?

Legacy Knowledge Base