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

Error SOAP message MUST NOT contain a Document Type Declaration"

SA-547

Summary



When execute the connect soap following error we are getting after sending the request
SOAP message MUST NOT contain a Document Type Declaration(DTD)

Error Messages



More details from log

2014-08-15 12:42:40,866 [127.0.0.1-21006-10] [ STANDARD] [ application:00.00.00] (ngineinterface.service.HttpAPI) ERROR server|ip
com.pega.pegarules.pub.PRRuntimeError
com.pega.pegarules.pub.PRRuntimeError: PRRuntimeError
at com.pega.pegarules.session.internal.mgmt.base.ThreadRunner.runActivitiesAlt(ThreadRunner.java:683)
at com.pega.pegarules.session.internal.mgmt.PRThreadImpl.runActivitiesAlt(PRThreadImpl.java:581)
at com.pega.pegarules.session.internal.engineinterface.service.HttpAPI.runActivities(HttpAPI.java:2366)
at com.pega.pegarules.session.external.engineinterface.service.EngineAPI.processRequestInner(EngineAPI.java:394)
at sun.reflect.GeneratedMethodAccessor79.invoke(Unknown Source)
...
Caused by: com.pega.pegarules.pub.services.RemoteApplicationException: SOAP service failed
...
Caused by: com.pega.apache.axiom.om.OMException: SOAP message MUST NOT contain a Document Type Declaration(DTD)
at com.pega.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.createDTD(StAXSOAPModelBuilder.java:461)
at com.pega.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:279)
at com.pega.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.getSOAPEnvelope(StAXSOAPModelBuilder.java:204)
at com.pega.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.<init>(StAXSOAPModelBuilder.java:154)
at com.pega.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.<init>(StAXSOAPModelBuilder.java:140)
at com.pega.apache.axis2.builder.BuilderUtil.getSOAPBuilder(BuilderUtil.java:686)
at com.pega.apache.axis2.transport.TransportUtils.createDocumentElement(TransportUtils.java:215)
at com.pega.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:145)
at com.pega.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:108)
... 60 more


Steps to Reproduce



Invoke the SOAP connector in PRPC


Root Cause



The request header is missing

Resolution



Passing the header to the request using XML stream rule
Suggest Edit

Published November 6, 2015 - Updated October 8, 2020

Did you find this content helpful? Yes No

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.

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