Issue 4082 Fix ResourceAccessException retry for network connectivity errors #4094
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
#4082
Network connectivity errors like "HTTP/1.1 header parser received no bytes" were not being retried across all Spring AI model providers. These
ResourceAccessException errors occurred during poor network conditions but failed immediately instead of utilizing the existing retry mechanism.
Solution
Added ResourceAccessException.class to both DEFAULT_RETRY_TEMPLATE and SHORT_RETRY_TEMPLATE in RetryUtils.java. This enables automatic retry of
network-level connectivity issues with the same exponential backoff strategy used for other transient errors.
Impact
Manually verified with MockWebServer that ResourceAccessException is now properly retried and succeeds after network errors are resolved.
Signed-off-by: Mattia Pasetto matpat17@gmail.com
I am still pretty new to contributions, please double check and let me know of any errors.