Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

SAXParseException: Content is not allowed in prolog



When opening rules in Pega Designer Studio or the Case Manager portal, error occurs and the UI or the rules display incorrectly in the Stage environment. Pega application is deployed in the WebSphere Application Server (WAS).

Error Messages InvalidStream, StorageStream)    sax parse error: Content is not allowed in prolog.


Caused by: org.xml.sax.SAXParseException: Content is not allowed in prolog.

Steps to Reproduce

  1. Log in to the application.
  2. Open the rules to navigate through the system.

Root Cause

HTTP Request is corrupted before it reaches the Pega application. In the HTTP POST body, null characters are received. Hence, the application cannot process the expected response. Therefore, the attachments on the work object are not displayed.

In the PegaRules logs, SAX Parse error or SAXParseException occurred. According to the IBM WebSphere logs, the InputStream is read twice. Hence, when the second read happens, there is no data in the POST body for the Pega Engine to parse the Request. This lead to the SAX Parse Exception in the PegaRules log file.


Make the following WAS configuration change to enable the rereading of the POST data. = true

Published June 3, 2020 - Updated December 2, 2021

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us