Legacy Knowledge Base
Published Jul. 2, 2025

DocumentException in UpgradeMVCCVersion when running upgrades from Gogo Shell

Written By

Cristina Rodriguez

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 running certain upgrade processes from the Gogo Shell using upgrade:execute, a DocumentException is observed:

    com.liferay.portal.kernel.upgrade.UpgradeException: com.liferay.portal.kernel.xml.DocumentException
    {...}
    Caused by: com.liferay.portal.kernel.xml.DocumentException
    at com.liferay.portal.xml.SAXReaderImpl.read(SAXReaderImpl.java:372)
    at com.liferay.portal.xml.SAXReaderImpl.read(SAXReaderImpl.java:346)
    at com.liferay.portal.kernel.xml.UnsecureSAXReaderUtil.read(UnsecureSAXReaderUtil.java:46)
    at com.liferay.portal.kernel.upgrade.UpgradeMVCCVersion.getClassElements(UpgradeMVCCVersion.java:98)
    

Environment

  • Liferay DXP upgrades using the Gogo shell

Resolution

  1. (Optional) Use the upgrade:check Gogo shell command to identify which module(s) upgrade is pending. You can attempt upgrading it individually using upgrade:execute[module_name].
  2. If the error persists, you must stop your Liferay server and perform the pending upgrade processes using the bundle's Database Upgrade Tool.

Once the pending processes complete, the DocumentException no longer appears.

Additional Information

Did this article resolve your issue ?

Legacy Knowledge Base