Getting NullPointerException in LocalizationImpl class during upgrade
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
- The following error appears during the upgrade from Liferay Portal 6.2 to Liferay DXP 7.4.
2022-08-24 06:06:09.974 ERROR [main][LocalizationImpl:896] null
java.lang.NullPointerException: null
at com.liferay.portal.util.LocalizationImpl.getXml(LocalizationImpl.java:868) ~[portal-impl.jar:?]
at com.liferay.portal.util.LocalizationImpl.updateLocalization(LocalizationImpl.java:1141) ~[portal-impl.jar:?]
at com.liferay.portal.kernel.util.LocalizationUtil.updateLocalization(LocalizationUtil.java:384) ~[portal-kernel.jar:?]
at com.liferay.portal.upgrade.v7_0_0.UpgradeGroup.updateGroupsNames(UpgradeGroup.java:149) ~[portal-impl.jar:?]
at com.liferay.portal.upgrade.v7_0_0.UpgradeGroup.doUpgrade(UpgradeGroup.java:55) ~[portal-impl.jar:?]
at com.liferay.portal.kernel.upgrade.UpgradeProcess.lambda$upgrade$0(UpgradeProcess.java:101) ~[portal-kernel.jar:?]
at com.liferay.portal.db.partition.DBPartitionUtil.forEachCompanyId(DBPartitionUtil.java:118) ~[portal-impl.jar:?]
at com.liferay.portal.dao.db.BaseDB.process(BaseDB.java:356) ~[portal-impl.jar:?]
at com.liferay.portal.kernel.dao.db.BaseDBProcess.process(BaseDBProcess.java:390) ~[portal-kernel.jar:?]
at com.liferay.portal.kernel.upgrade.UpgradeProcess.upgrade(UpgradeProcess.java:88) ~[portal-kernel.jar:?]
at com.liferay.portal.kernel.upgrade.UpgradeProcess.upgrade(UpgradeProcess.java:129) ~[portal-kernel.jar:?]
at com.liferay.portal.upgrade.UpgradeProcess_7_0_0.doUpgrade(UpgradeProcess_7_0_0.java:121) ~[portal-impl.jar:?]
at com.liferay.portal.kernel.upgrade.UpgradeProcess.lambda$upgrade$0(UpgradeProcess.java:101) ~[portal-kernel.jar:?]
at com.liferay.portal.db.partition.DBPartitionUtil.forEachCompanyId(DBPartitionUtil.java:118) [portal-impl.jar:?]
at com.liferay.portal.dao.db.BaseDB.process(BaseDB.java:356) [portal-impl.jar:?]
at com.liferay.portal.kernel.dao.db.BaseDBProcess.process(BaseDBProcess.java:390) [portal-kernel.jar:?]
at com.liferay.portal.kernel.upgrade.UpgradeProcess.upgrade(UpgradeProcess.java:88) [portal-kernel.jar:?]
at com.liferay.portal.kernel.upgrade.util.UpgradeProcessUtil._upgradeProcess(UpgradeProcessUtil.java:160) [portal-kernel.jar:?]
at com.liferay.portal.kernel.upgrade.util.UpgradeProcessUtil.upgradeProcess(UpgradeProcessUtil.java:136) [portal-kernel.jar:?]
at com.liferay.portal.events.StartupHelperUtil.upgradeProcess(StartupHelperUtil.java:173) [portal-impl.jar:?]
at com.liferay.portal.tools.DBUpgrader.upgradePortal(DBUpgrader.java:233) [portal-impl.jar:?]
at com.liferay.portal.tools.DBUpgrader.main(DBUpgrader.java:137) [portal-impl.jar:?]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_191]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_191]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_191]
at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_191]
Resolution
- The observed behavior is a known Liferay DXP bug.
- If the hotfix is required for this issue, please create a support ticket requesting the hotfix by attaching the patch details.
-
Installing a hotfix will guide to installation of the hotfix in the respective environment.
Did this article resolve your issue ?