Comment 16 for bug 339872

I forgot to check the latest dcpp trunk as well. However, are you sure that the best way to fix is to change the Exception specification from SocketException to Exception? Wouldn't it be better to handle it locally if possible and continue as my fix attempts? The code already handles an invalid return value from UNZFilter so I'd assume it should be able to handle catching the exception similarly.