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

AES could not parse SOAP envelope and throws PRException in log



User gets an error " Couldn't parse SOAP request envelope" written to the PegaRULES.log for their AES instances. 

Error Messages

2014-10-07 10:47:02,590 [ WebContainer : 8] [ STANDARD] [ ] ( services.soap.SOAPService) ERROR XXXXXX| - Couldn't parse SOAP request envelope Couldn't parse SOAP request envelope
From: (unknown)
at com.pega.pegarules.integration.engine.internal.util.SOAPUtils.parseRequestData(
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl._invokeEngine_privact(
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl.invokeEngine(
at com.pega.pegarules.session.internal.engineinterface.etier.ejb.EngineBean.invokeEngine(
at sun.reflect.GeneratedMethodAccessor50.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(
at java.lang.reflect.Method.invoke(
Caused by:
org.xml.sax.SAXParseException: Attribute "encodingStyle" bound to namespace "" was already specified for element "ns1:logAlert".
at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source)
at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl.parse(Unknown Source)
at com.pega.pegarules.integration.engine.internal.util.SOAPUtils.parseRequestData(
... 45 more

Steps to Reproduce

Error manifests during AES alert processing.

Root Cause

User has set the logger  'com.pega.pegarules.integration.engine.internal.util.SOAPUtils' to debug mode that resulted in finding the root cause of error as there were two encoding styles tags coming with SOAP request envelope. Issue could be related to caching in Axis stack. Older version of Axis library being used by PRPC (as observed from SMA under 'Advanced-ETier runtime environment' checking for the class name 'com.pega.apache.axis.client.Call') for SOAP connections. 


User was suggested to upgrade Axis library (new praxis2-1.6.2.jar) in AES and switch the AES connectors to use the same library.


Published January 31, 2016 - 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