|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.
OK so I think the core issue is that org.jenkinsci.remoting.nio.NioChannelHub.java's line 513 is:
if (key.isReadable()) {
where as I think it should be:
if (key.isValid() && key.isReadable()) {
I guess this would fix the issue assuming that selectedKeys().iterator() is thread safe (I don't really know much about nio), actually it probably makes sense just to add a catch to one of the handlers in the same method (I think the one at http://git.io/VtniaQ).
Basically my thoughts as to what's happening is that isReadable is generating a CancelledKeyException which ends up getting caught by the RuntimeException handler (at http://git.io/l-5MhA) which ends up killing the loop and attempts to abort everything, including the selector that's not-valid (which gives the message in the description).