Closed epoll server socket channel still accepting connections.

53 views
Skip to first unread message

Luke Daley

unread,
Jun 16, 2016, 7:06:07 AM6/16/16
to ne...@googlegroups.com
Hi,

Does anyone know of any issues with epoll server socket channels continuing to accept incoming requests after channel close? The same code refuses new connections when not using the epoll transport.

I’m issuing channel.close().sync(), yet new connections are still being accepted.

I’m using 4.1.0.CR7. 


Norman Maurer

unread,
Jun 16, 2016, 7:12:45 AM6/16/16
to ne...@googlegroups.com
Nope… Could you please open an issue and as best also include a reproducer ?

Thanks Luke!

-- 
You received this message because you are subscribed to the Google Groups "Netty discussions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to netty+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/netty/CAKn7%3D%2B%3DB6_eAeayY6M6e4DLCcG%2BSvyLOaDni6GSopVE_6B1L6Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Norman Maurer

unread,
Jun 16, 2016, 7:52:52 AM6/16/16
to ne...@googlegroups.com
Just tested it with 4.1 branch and it works as expected. Maybe try upgrade and see if it fix it ?

Luke Daley

unread,
Jun 16, 2016, 8:56:21 PM6/16/16
to ne...@googlegroups.com

The same happens with 4.1.1.Final. 

Norman Maurer

unread,
Jun 16, 2016, 11:40:03 PM6/16/16
to ne...@googlegroups.com
 I was not able to to reproduce it. Can you procide a reproducer?
--
You received this message because you are subscribed to the Google Groups "Netty discussions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to netty+un...@googlegroups.com.

Luke Daley

unread,
Jul 23, 2016, 3:27:20 AM7/23/16
to Netty discussions
I've finally worked out what was going on here. It turns out that it was, unsurprisingly, a problem with my code. 

I had a test which effectively started then stopped a HTTP server app, then asserted that it eventually stopped accepting requests. This was done in parallel. There was an unlikely race in the test that meant a request may have made it before the shutdown was issued. This, combined with the fact that I didn't realise that the HTTP client I was using to test supported keep alive was the problem. The app was indeed rejecting new connections, but the requesting loop was reusing the open connection each time.

Cheers.

Norman Maurer

unread,
Jul 23, 2016, 4:01:34 AM7/23/16
to ne...@googlegroups.com
Thanks for closing the loop
Reply all
Reply to author
Forward
0 new messages