MuleSoft · Web Service Consumer Connector
WSC:SOAP_FAULT
Short answer
WSC:SOAP_FAULT means the SOAP service returned a fault, or the response did not match the format in the WSDL. Read the fault text in error.errorMessage.payload.reason and the detail in error.errorMessage.payload.detail.
VerifiedLast verified
01Error text
Error type: WSC:SOAP_FAULT02Likely causes
- Error matching the SOAP response with the format provided by the WSDL.
- Every CXF SOAP fault error is wrapped in a
WSC:SOAP_FAULT.
03How to fix it
- In an error handler, read
error.errorMessage.payload.reasonfor the fault text anderror.errorMessage.payload.detailfor the fault detail. - Read
error.errorMessage.attributes.statusCodeanderror.errorMessage.attributes.headersfor the HTTP status and headers. - Turn on wire logging for the HTTP transport: in
log4j2.xmladd<AsyncLogger name="org.mule.service.http.impl.service.HttpMessageLogger" level="DEBUG" />. - Correct the request so the service accepts it.
- Handle the failure with an error handler of type
WSC:SOAP_FAULT.
04Official documentation
→Related errors
- WSC:SOAP_FAULT with faultcode soap:MustUnderstandA WSC:SOAP_FAULT with the fault code soap:MustUnderstand happens because the connector's security Must Understand field defaults to true and the service does not process that header. Set Must Understand to false.
- WSC:BAD_REQUESTWSC:BAD_REQUEST means the operation does not exist in the WSDL, or the request body is not valid XML. Pick an operation the WSDL defines and build the body as well-formed XML.
- WSC:CANNOT_DISPATCHWSC:CANNOT_DISPATCH is raised when the request cannot be dispatched and the HTTP error cannot be turned into a SOAP fault. In version 3.0 that covers one-way operations, WSDL or schema requests, an empty HTTP error body, or an error body over 1048576 bytes.
Test every fix in a non-production environment before you apply it to production. See how entries are verified.
More for MuleSoft work:Open MuleSoft jobsMuleSoft rates and salariesHire a senior MuleSoft developer