Simpler to catch ReadPendingException in just one place.
@@ -105,12 +105,6 @@ class PlainCLIProtocol {
} catch (EOFException x) {
handleClose();
break; // TODO verify that we hit EOF immediately, not partway into framelen
- } catch (ReadPendingException x) {
- LOGGER.log(Level.FINE, null, x);
- // TODO what does this signify? Seems to be thrown randomly by org.eclipse.jetty.io.FillInterest.register. No obvious impact.
- // Check https://github.com/eclipse/jetty.project/issues/1047 in 9.4.3.v20170317 but cf. https://github.com/joakime/jetty-async-bug/issues/1
- handleClose();
- break;
}
if (framelen < 0) {
throw new IOException("corrupt stream: negative frame length");
@@ -140,8 +134,10 @@ class PlainCLIProtocol {
}
} catch (IOException x) {
LOGGER.log(Level.WARNING, null, flightRecorder.analyzeCrash(x, "broken stream"));
- } catch (ReadPendingException x) { // as above
+ } catch (ReadPendingException x) {
LOGGER.log(Level.FINE, null, x);
+ // TODO what does this signify? Seems to be thrown randomly by org.eclipse.jetty.io.FillInterest.register. No obvious impact.
+ // Check https://github.com/eclipse/jetty.project/issues/1047 in 9.4.3.v20170317 but cf. https://github.com/joakime/jetty-async-bug/issues/1
handleClose();
}
}
