Support Article
Connect SOAP MTOM xop 3.2.2.a: xop:Include must be sole child
SA-33715
Summary
The user is experiencing an issue transmitting binary data using an MTOM SOAP service. The SOAP request is set up correctly; InvokeAxis2 is generating an MTOM message. Using HTTP Client Wire tracing, the user captured the SOAP message and discovered that the XML is malformed. Installing HFix-28742 did not resolve the problem, as explained in SA-26447, https://pdn.pega.com/support-articles/connect-soap-mtom-enabled-fails-after-upgrade-721.
Error Messages
xop 3.2.2.a: xop:Include must be the sole child of element {http://a.b.c.d/CIM/Common/2}Document of type {http://a.b.c/2001/XMLSchema}base64Binary
Steps to Reproduce
- Create and invoke a SOAP call with MTOM enabled.
See the XOP error. - Search the PDN for Pega 7.2.1 Troubleshooting information and find SA-26447.
- Request and install HFix-28742.
See the XOP error again.
Root Cause
A software use or operation error
HFix-28742 requires pre-installation steps, which are documented in the HFix ReadMe.
See the Root Cause explained in SA-26447, https://pdn.pega.com/support-articles/connect-soap-mtom-enabled-fails-after-upgrade-721.
Resolution
Apply HFix-28742, but be sure to complete the required steps before you install the hotfix:
- Back up your database.
- Run the following SQL query to remove the references to faulty classes:
Delete from pr_engineclasses where pzjar like 'webservices-rt.jar' - Install HFix-28742.
- Restart the server.
.
Published September 8, 2017 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.