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

SOAP Service throws PRRuntimeError and SAXParseException



User experiences with PRRuntimeError and SAXParseException, while running a SOAP Service.

Error Messages

2014-07-01 00:05:00,899 [fault (self-tuning)'] [  STANDARD] [        Demo:0.0.0] (ngineinterface.service.HttpAPI) ERROR Application1|  - PRRuntimeError
                at com.pega.pegarules.session.internal.mgmt.base.ThreadRunner.runActivitiesAlt(
                at com.pega.pegarules.session.internal.mgmt.PRThreadImpl.runActivitiesAlt(
2014-09-18 00:02:01,675 [fault (self-tuning)'] [  STANDARD] [        PegaDM:06.03] (     mapping.xml.XMLParserBase) ERROR Application1|   - Caught exception parsing XML stream
org.xml.sax.SAXParseException: The entity name must immediately follow the '&' in the entity reference.           

Steps to Reproduce

Run a SOAP Service with Decision Table.
Pass wrong values by including special characters as '&'.

Root Cause

Issue was due to parsing special character '&'  in the input text parameter.


User has to pre-process/escape the special characters (in this case, it was '&') in Service Request  XML before sending it to PRPC SOAP Service.

Suggest Edit

Published January 31, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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