Details
-
Bug
-
Status: Open
-
Critical
-
Resolution: Unresolved
-
1.5.5
-
None
-
None
-
Linux
Description
Problem:
During testing in some occasions we have experienced 503 response from service which did leave the sockets in CLOSE_WAIT state.
After extending HTTPSender in method handleResponse to check for the SC_SERVICE_UNAVAILABLE in the same way as for SC_INTERNAL_SERVER_ERROR and SC_BAD_REQUEST problem seams to disappear.
Possible solution:
class: HTTPSender
method: handleResponse
Existing:
method.releaseConnection();
} else if (statusCode == HttpStatus.SC_INTERNAL_SERVER_ERROR
statusCode == HttpStatus.SC_BAD_REQUEST)
{
// Save the HttpMethod so that we can release the connection when cleaning up
msgContext.setProperty(HTTPConstants.HTTP_METHOD, method);
Updated:
method.releaseConnection();
}
else if (statusCode == HttpStatus.SC_INTERNAL_SERVER_ERROR |
---|
statusCode == HttpStatus.SC_SERVICE_UNAVAILABLE |
statusCode == HttpStatus.SC_BAD_REQUEST) { // Save the HttpMethod so that we can release the connection when cleaning up msgContext.setProperty(HTTPConstants.HTTP_METHOD, method); |