You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I suspect that leased connections are not released back into the connection pool when an error is encountered, and the Apache HTTP client is used in combination with the retry filter. I think it is because the response body is not read before throwing a RetryException.
It seems that if something like the following is added to RetryFilterFunctions, right before this line of code, the connections get released back again:
Describe the bug
I suspect that leased connections are not released back into the connection pool when an error is encountered, and the Apache HTTP client is used in combination with the retry filter. I think it is because the response body is not read before throwing a RetryException.
It seems that if something like the following is added to RetryFilterFunctions, right before this line of code, the connections get released back again:
Sample
Here is a repo that reproduces the issue: https://github.com/johan1a/spring-cloud-gateway-mvc-connection-test/tree/master
The text was updated successfully, but these errors were encountered: