MuleSoft · Web Service Consumer Connector
WSC:BAD_REQUEST
Short answer
WSC: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.
VerifiedLast verified
01Error text
Error type: WSC:BAD_REQUEST02Likely causes
- The Web Service Consumer Connector operation does not exist in the WSDL.
- The request body is not a valid XML.
03How to fix it
- Check that the configured operation name exists in the WSDL for the selected service and port.
- Check that the body the Consume operation receives is well-formed XML for that operation.
- Turn on wire logging for the HTTP transport: in
log4j2.xmladd<AsyncLogger name="org.mule.service.http.impl.service.HttpMessageLogger" level="DEBUG" />. - Handle the failure with an error handler of type
WSC:BAD_REQUEST.
04Official documentation
→Related errors
- WSC:INVALID_WSDLWSC:INVALID_WSDL means the WSDL is poorly formatted. Validate the WSDL in a viewer and, if it is loaded from a remote host, confirm the app can reach that host.
- WSC:SOAP_FAULTWSC: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.
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