Handle ClosedSelectorException also from Selector.keys

[jglick]

I see this printed at the end of (passing) functional tests, which seems to be pure noise:

… hudson.util.ExceptionCatchingThreadFactory uncaughtException
WARNING: Thread Computer.threadPoolForRemoting [#1] terminated unexpectedly
java.nio.channels.ClosedSelectorException
	at sun.nio.ch.SelectorImpl.keys(SelectorImpl.java:68)
	at org.jenkinsci.remoting.protocol.IOHub.run(IOHub.java:422)
	at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:748)

We were already handling this exception from various calls in the inner try block—but not from the Selector.keys call used to set Thread.name.

@reviewbybees

[ghost]

This pull request originates from a CloudBees employee. At CloudBees, we require that all pull requests be reviewed by other CloudBees employees before we seek to have the change accepted. If you want to learn more about our process please see this explanation.

[jglick]

Linux:

The forked VM terminated without properly saying goodbye. VM crash or System.exit called?

Windows:

Execution version-property of goal org.codehaus.mojo:build-helper-maven-plugin:1.7:regex-property failed: Illegal group reference

[oleg-nenashev]

#worksonmymachine

[oleg-nenashev]

🐝 from what I see. Will manually test before the release

[oleg-nenashev]

@reviewbybees done