-
-
Notifications
You must be signed in to change notification settings - Fork 15.9k
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
Epoll client's connect future with ALLOW_HALF_CLOSURE enabled reports success on failed connection #3785
Comments
@normanmaurer - I'll give this to you :) |
@Scottmitch you are so good too me ;) |
@rkapsi do you grant us to include your test-case into netty ? |
@normanmaurer - yes of course. |
Thanks! Working on a fix
|
Motivation: Due a bug we not correctly handled connection refused errors and so failed the connect promise with the wrong exception. Beside this we some times even triggered fireChannelActive() which is not correct. Modifications: - Add testcase - correctly detect connect errors Result: Correct and consistent handling.
Motivation: Due a bug we not correctly handled connection refused errors and so failed the connect promise with the wrong exception. Beside this we some times even triggered fireChannelActive() which is not correct. Modifications: - Add testcase - correctly detect connect errors Result: Correct and consistent handling.
Motivation: Due a bug we not correctly handled connection refused errors and so failed the connect promise with the wrong exception. Beside this we some times even triggered fireChannelActive() which is not correct. Modifications: - Add testcase - correctly detect connect errors Result: Correct and consistent handling.
Motivation: Due a bug we not correctly handled connection refused errors and so failed the connect promise with the wrong exception. Beside this we some times even triggered fireChannelActive() which is not correct. Modifications: - Add testcase - correctly detect connect errors Result: Correct and consistent handling.
Motivation: Due a bug we not correctly handled connection refused errors and so failed the connect promise with the wrong exception. Beside this we some times even triggered fireChannelActive() which is not correct. Modifications: - Add testcase - correctly detect connect errors Result: Correct and consistent handling.
@rkapsi should be fixed now... Please reopen if you still think it is an issue. Thanks again for reporting and the test-case! |
@normanmaurer: confirm. My canary test started passing (or rather failing) as soon as the new SNAPSHOT went live. Thanks! |
Awesome. Thanks!
|
Motivation: Due a bug we not correctly handled connection refused errors and so failed the connect promise with the wrong exception. Beside this we some times even triggered fireChannelActive() which is not correct. Modifications: - Add testcase - correctly detect connect errors Result: Correct and consistent handling.
The connect ChannelFuture of an Epoll client that has ALLOW_HALF_CLOSURE enabled reports success and doesn't raise an Exception. The Channel says it's active and even the ChannelHandler's methods such as channelActive() get called.
There is an exception under the hood (see below) but it's not getting exposed to the user. An unit test is attached (see below).
Exception
Unit Test
Log Output
The text was updated successfully, but these errors were encountered: