Skip to content

Fix for NPE when connection is reset by peer #1771

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

rachid-o
Copy link
Contributor

@rachid-o rachid-o commented Feb 9, 2021

A fix for the NullPointerException problem reported in #1769
It looks like the NPE is introduced as programming error. because there is a null check on channel, but in the body it uses future.channel() which potential returns null.

I ca't oversee the impact of this change, but all tests pass when running mvn clean verify on my machine.

@rachid-o rachid-o force-pushed the bugfix/1769-NPE-connection-reset branch from 0da63b5 to 15a6f92 Compare February 10, 2021 18:55
@rachid-o rachid-o force-pushed the bugfix/1769-NPE-connection-reset branch from 15a6f92 to 37adafe Compare February 10, 2021 19:25
…thub

Also the duration of running the build in Github varies
@yazgoo
Copy link

yazgoo commented Mar 11, 2021

Hi, thanks for the fix ! any idea of when this can be merged ? I've also had instances where this error came up

@rachid-o
Copy link
Contributor Author

@TomGranot is there anything I can do to help to get this fix merged?

@TomGranot TomGranot merged commit d2fc371 into AsyncHttpClient:master Mar 27, 2021
@TomGranot
Copy link
Contributor

@yazgoo @rachidbm Merged. Sorry for the wait!

@TomGranot
Copy link
Contributor

Some issues this closes:

#1769
#1779

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants