Troubleshooting
Problem
While in the middle of a 8.2.1 -> 9.5 upgrade, The customer site is getting malformed XML errors from the IS when the application is consuming services in 9.5, but no issues in 8.2.1.
Client has identified that the node name is missing in the XML as shown below. This malformed XML does not work in 9.5, but it works for 8.2.1.
Client understands the long term solution is to fix the XML by adding the node name, but given the migration schedule, they require a quick temporary solution while the long-term one is being in development.
Invalid in 9.5, but valid in 8.2
<soapenv:Header>
< soapenv:actor="http://schemas.xmlsoap.org/soap/actor/next" soapenv:mustUnderstand="0"/>
</soapenv:Header>
Below is the error seen:
com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character ' ' (code 32) in content after '<' (malformed start element?).
at [row,col {unknown-source}]: [1,193]
Caused by: org.apache.axiom.om.OMException: com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character ' ' (code 32) in content after '<' (malformed start element?).
at [row,col {unknown-source}]: [1,193]
Caused by: com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character ' ' (code 32) in content after '<' (malformed start element?).
at [row,col {unknown-source}]: [1,193]
Have tried to add the following watt settings and restarted the IS, but that hasn’t helped:
watt.server.xml.enforceEntityRef=false
watt.core.schema.validateIncomingXSDUsingXerces=false
watt.server.wsdl.validateWSDLSchemaUsingXerces=false
Document Location
Worldwide
Log InLog in to view more of this document
Was this topic helpful?
Document Information
Modified date:
20 March 2025
UID
ibm17220527