Fixed an issue in async client causing resposne future to get stuck

[zoewangg]

Motivation and Context

#4354 #3335
If there is a server error and the server fails to return response body that matches with the content length specified in the response header, the response future will get stuck. This is because we are not invoking onError for errorResponseHandler that is supposed to fail the return future.

Modifications

Invoke errorResponseHandler#onError when onError is invoked.

Testing

Added functional test

Screenshots (if appropriate)

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)

Checklist

• I have read the CONTRIBUTING document
• Local run of mvn install succeeds
• My code follows the code style of this project
• My change requires a change to the Javadoc documentation
• I have updated the Javadoc documentation accordingly
• I have added tests to cover my changes
• All new and existing tests passed
• I have added a changelog entry. Adding a new entry must be accomplished by running the scripts/new-change script and following the instructions. Commit the new file created by the script in .changes/next-release with your changes.
• My change is to implement 1.11 parity feature and I have updated LaunchChangelog

License

• I confirm that this pull request can be released under the Apache 2 license

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
3 Code Smells

100.0% Coverage
0.0% Duplication