MuleSoft · HTTP Connector
HTTP:INTERNAL_SERVER_ERROR
Short answer
HTTP:INTERNAL_SERVER_ERROR means the server hit a situation that prevented it from fulfilling the request the HTTP Request operation sent (HTTP 500). Read the response body and the remote system's logs to find what failed there.
VerifiedLast verified
01Error text
Error type: HTTP:INTERNAL_SERVER_ERROR02Likely causes
- The server encountered a situation that prevented it from fulfilling the request.
- HTTP Connector treats any status code from 500 through 599 as a failure and raises an error.
03How to fix it
- Turn on HTTP wire logging to see the exact request and response: in
log4j2.xml, enable the loggerorg.mule.service.http.impl.service.HttpMessageLoggeratDEBUGlevel. Read the response body, which may carry the remote system's own error detail. - Check the logs of the remote system for the same time. The failure happened there.
- Confirm that the request body and parameters are what that system expects. Some servers answer 500 to input they cannot process.
- Handle the failure with an error handler of type
HTTP:INTERNAL_SERVER_ERROR.
04Official documentation
→Related errors
- HTTP:SERVICE_UNAVAILABLEHTTP:SERVICE_UNAVAILABLE means the server could not handle the request because it is down for maintenance or overloaded (HTTP 503). The fault is on the remote side, so retry after a delay and handle the error if the service stays down.
- HTTP:BAD_REQUESTHTTP:BAD_REQUEST means the server could not understand the request the HTTP Request operation sent because its syntax was invalid (HTTP 400). Log the outgoing request, compare it with what the server expects, and correct the body, headers or parameters.
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