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

MuleSoft error
Error type: WSC:BAD_REQUEST

02Likely 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

  1. Check that the configured operation name exists in the WSDL for the selected service and port.
  2. Check that the body the Consume operation receives is well-formed XML for that operation.
  3. Turn on wire logging for the HTTP transport: in log4j2.xml add <AsyncLogger name="org.mule.service.http.impl.service.HttpMessageLogger" level="DEBUG" />.
  4. Handle the failure with an error handler of type WSC:BAD_REQUEST.

04Official documentation

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

The iPaaS Brief

Subscribe to The iPaaS Brief.

The iPaaS newsletter for the people who run integrations. From iPaaS Group.

Free. You finish on theipaasbrief.com and confirm by email.