If it wasn't clear (re-reading my last message I guess it wasn't); yes this represents a different variant to issue initially presented in JENKINS-22932, basically a different exception get's thrown which I think I've fixed in the pull request above, it's probably possible to refactor the fix for both issues in such a way that other exceptions don't kill the main NIO/select loop in the future but this specific issue can be fixed without that (it's easier for you guys to review this anyways).

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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to