Why does the inReady method of StreamDecoder swallow IOException?

Jeff Evans jeffrey.wayne.evans at gmail.com
Wed Nov 15 23:11:37 UTC 2017


We are dealing with an issue where an underlying exception appears to
be getting swallowed by the StreamDecoder class.  In particular, the
Jersey client library we are using (which happens to be version
2.25.1) is throwing an IOException out of its implementation of


by way of calling checkThrowable


The caller of that is ultimately StreamDecoder#inReady.  We are seeing
the problem under Oracle JDK 1.8.0_121, but it seems the StreamDecoder
code hasn't changed in a while:

Is there some issue with the way the Jersey library code
implementation, or potentially some issue with our code that is
resulting in this exception not being propagated out from
StreamDecoder?  Any insight is appreciated.

Full stack trace image here: https://i.imgur.com/AuyYFAp.png

More information about the jdk-dev mailing list