Tunnel socket can be closed allowing for infinite high CPU loop that doesn't realize its closed.

Socket apparently gets closed after some time...maybe a week or two, and the tunnel doesn't realize tis closed. Just keeps throwing socket closed exceptions, which are consumed and it checks if the "stub" is closed, tis not, so it loops again, no delay, CPU shoots to 100%. Server is unusable.

Tunnel.java line 246, 247, 248. Needs to catch a socket closed exception and break, not loop.