Legacy Knowledge Base
Published Jul. 2, 2025

DocumentException during upgrade process while reading META-INF/portal-hbm.xml

Written By

Cristina Rodriguez

How To articles are not official guidelines or officially supporteddocumentation. They are community-contributed content and may not alwaysreflect the latest updates to Liferay DXP. We welcome your feedback toimprove How to articles!

While we make every effort to ensure this Knowledge Base is accurate, itmay not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with anyfeedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack"publication program, made available for informational purposes. Articlesin this program were published without a requirement for independentediting or verification and are provided "as is" withoutguarantee.

Before using any information from this article, independently verify itssuitability for your situation and project.

Issue

  • A DocumentException is thrown at certain point when you run the upgrade process from the Gogo Shell using command upgrade:run or upgrade:runAll
  • You can find a stack trace similar to the following in the upgrade.log:
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

  • Reproducible during any upgrade process.

Resolution

    • We have seen this error when some pending upgrade process is executed from the Gogo Shell.
    • Stop your server and run the pending processes through the provided script db_upgrade.sh. This way the exception should no longer be thrown.

Additional Information

 

 

 

Did this article resolve your issue ?

Legacy Knowledge Base