Legacy Knowledge Base
Published Sep. 10, 2025

Getting 400 error code while accessing adaptive media urls using public IP

Written By

Dávid Hegedüs

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

ERROR [http-nio-8080-exec-10][TrashEntryServiceImpl:114] com.liferay.portal.kernel.exception.SystemException: Couldn't initialize a SAX driver to create an XMLReader
com.liferay.portal.kernel.exception.SystemException: Couldn't initialize a SAX driver to create an XMLReader
 at com.liferay.portal.store.s3.S3Store.transform(S3Store.java:902)
 at com.liferay.po

Environment

  • Liferay DXP 7.2 vanilla setup with S3 integration

Resolution

  • To resolve this issue, a SAXParser should be defined manually to fix the SAXParser errors while working with S3Store.
  • Step 1:
    • If you are using an app server like Apache Tomcat, then the below property should be included in a system-ext.properties file and place it under /WEB-INF/classes/ in the Liferay DXP installation’s classpath. Restart the server.
org.xml.sax.driver=com.sun.org.apache.xerces.internal.parsers.SAXParser
  • Step 2: 
    • Open the dev-tools console in the browser
    • Navigate to the Network tab, 
    • Check the Disable cache box, and reloading the adaptive media URL directly, the image could be reached.

Additional Information

 

Did this article resolve your issue ?

Legacy Knowledge Base