Error via Parsing XML:)Fatal Error Found: Content is not allowed in prolog
Hi Team,
We are getting the below error while parsing the SOAP Response via Parse XML.
** Fatal Error Found: Content is not allowed in prolog. Throwing an Exception ... ** FAIL : Unable to apply Rule-Parse-XML instance. Caught exception parsing XML stream
The <xml starting tag is not having any unneccessary character and UTF-8 encoding is present in all XSD and WSDL.
Kindly help us with some direction to solve the same
***Edited by Moderator Marije to add Support Case Details; update capability tags***
Pegasystems Inc.
GB
@ShwetaB96 without seeing the full error in your log file it is hard to comment.
Please could you take a look at the following support article in case it matches your environment:
https://community.pega.com/support/support-articles/sax-parse-error-content-not-allowed-prolog-2
The above article explanation for the reported behavior: This error will be thrown when Pega engine receivesan empty POST body from Tomcat or Websphere Application server container, which means request.getInputStream().read() returns 0 bytes. The reason for receiving the empty POST body is unknown because it happens in the Tomcat code or WebSphere Application Server code. To avoid this connector protocol needs to be changed as listed above.
Other questions:
Can you replicate this consistently?
The ' unable to parse' error can occur where the post data contains null or empty strings.
If you look in your logs and you see references to 'pyDeleteDocumentPg' could I suggest that you make sure that your 7.3.1 environment has the following hotfix installed:
@ShwetaB96 without seeing the full error in your log file it is hard to comment.
Please could you take a look at the following support article in case it matches your environment:
https://community.pega.com/support/support-articles/sax-parse-error-content-not-allowed-prolog-2
The above article explanation for the reported behavior: This error will be thrown when Pega engine receivesan empty POST body from Tomcat or Websphere Application server container, which means request.getInputStream().read() returns 0 bytes. The reason for receiving the empty POST body is unknown because it happens in the Tomcat code or WebSphere Application Server code. To avoid this connector protocol needs to be changed as listed above.
Other questions:
Can you replicate this consistently?
The ' unable to parse' error can occur where the post data contains null or empty strings.
If you look in your logs and you see references to 'pyDeleteDocumentPg' could I suggest that you make sure that your 7.3.1 environment has the following hotfix installed:
HFIX-50285 This was created for errors relating to : SAXParseException: Content is not allowed in prolog For scenarios where the queryString in the log file shows the pyDeleteDocumentPg being referenced.
The error results in an empty classless pyWorkPage during normal flow processing where the pyWorkPage should contain all of the normal case data. As a result, we get processes that run on a blank page and fail due to not having the correct data or class context to run appropriately.
com.pega.pegarules.pub.clipboard.InvalidStreamError: InvalidStream com.pega.pegarules.data.internal.clipboard.XMLStream.newStream(String, StorageStream) sax parse error: Content is not allowed in prolog . Caused by: org.xml.sax.SAXParseException: Content is not allowed in prolog.
These specific scenarios happens because of how Internet Explorer constructs an HTTP request - it sends the header and body of the request in separate TCP packets. In circumstances not known to us, the body packet goes missing. There is no graceful handling of this in engine - hence, the misleading Exception.
If you require further help I suggest that you log a support incident.
Please can you provide the INC number here so that we can help track the issue with you?
Infosys
IN
Hi Marjie , thanks a lot for your response .
Yes we are getting this error consistently when we try to parse the Response XML in Connect-SOAP having Validation checked as Always. Moreover we investigated the logs and it doesnt have references to 'pyDeleteDocumentPg'. Attaching the logs for your reference as well
Hi Marjie , thanks a lot for your response .
Yes we are getting this error consistently when we try to parse the Response XML in Connect-SOAP having Validation checked as Always. Moreover we investigated the logs and it doesnt have references to 'pyDeleteDocumentPg'. Attaching the logs for your reference as well
2022-06-22 15:09:54,536 [ WebContainer : 8] [ STANDARD] [ ] [Implementation:01.98] ( internal.util.PRParseUtils) ERROR - XML parsing failed com.pega.pegarules.pub.PRException: Caught exception parsing XML stream at com.pega.pegarules.integration.engine.internal.mapping.xml.XMLParserBase.parseDocument(XMLParserBase.java:512) ~[printegrint.jar:?] at com.pega.pegarules.integration.engine.internal.mapping.ParseRuleUtils.invokeXMLParseRule(ParseRuleUtils.java:248) ~[printegrint.jar:?] at com.pega.pegarules.integration.engine.internal.util.PRParseUtils.parseXML(PRParseUtils.java:119) ~[printegrint.jar:?] at com.pegarules.generated.activity.ra_action_runrulefrompage_d80e978a4f4351cec3caf4cfac2be555.step9_circum0(ra_action_runrulefrompage_d80e978a4f4351cec3caf4cfac2be555.java:1189) ~[?:?] at com.pegarules.generated.activity.ra_action_runrulefrompage_d80e978a4f4351cec3caf4cfac2be555.perform(ra_action_runrulefrompage_d80e978a4f4351cec3caf4cfac2be555.java:242) ~[?:?]
We are also raising an incident to Pega , will share the INC soon .
Do you suspect changing the server settings that are mentioned in the article can solve anything for us?
Padmasri Dr.B.V.Raju Institute of Technology
IN