Support Article
AES could not parse SOAP envelope and throws PRException in log
SA-3252
Summary
User gets an error "com.pega.pegarules.pub.PRException: 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|0.0.0.0 - Couldn't parse SOAP request envelope
com.pega.pegarules.pub.PRException: Couldn't parse SOAP request envelope
From: (unknown)
at com.pega.pegarules.integration.engine.internal.util.SOAPUtils.parseRequestData(SOAPUtils.java:367)
at com.pega.pegarules.integration.engine.internal.services.soap.SOAPService.invoke(SOAPService.java:393)
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl._invokeEngine_privact(EngineImpl.java:315)
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl.invokeEngine(EngineImpl.java:266)
at com.pega.pegarules.session.internal.engineinterface.etier.ejb.EngineBean.invokeEngine(EngineBean.java:239)
at sun.reflect.GeneratedMethodAccessor50.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
...
Caused by:
org.xml.sax.SAXParseException: Attribute "encodingStyle" bound to namespace "http://schemas.xmlsoap.org/soap/envelope/" 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(SOAPUtils.java:364)
... 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.
Resolution
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
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.