MuleSoft · Web Service Consumer Connector
WSC:EMPTY_RESPONSE
Short answer
WSC:EMPTY_RESPONSE occurs when mandatory fields are missing from the SOAP response (Illegal Empty Response). Inspect the HTTP status and headers on the error and check what the service actually returned.
VerifiedLast verified
01Error text
Error type: WSC:EMPTY_RESPONSE02Likely causes
- Mandatory fields are missing from the response (Illegal Empty Response).
03How to fix it
- In an error handler, read
error.errorMessage.attributes.statusCode,reasonPhraseandheaders. The payload is empty for this error. - Turn on wire logging for the HTTP transport: in
log4j2.xmladd<AsyncLogger name="org.mule.service.http.impl.service.HttpMessageLogger" level="DEBUG" />. - Check with the service owner why the response is empty.
- Handle the failure with an error handler of type
WSC:EMPTY_RESPONSE.
04Official documentation
→Related errors
- 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.
- 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