[Simon Roberts]

Chris, I'm OK with the idea that the program might be "operating in a
broken environment" but I find it had to accept the idea that "it's not a
crash" as useful. By the time the exception is thrown, I cannot access the
data. Merely telling the caller that there was an inconsistency in the
server (which I think we're assuming is true) has rendered the data
unreachable.

Since every other test mechanism at my disposal survives whatever
inaccuracy the node server is producing, it seems a bit ... well, let's say
"unforgiving" that this code treats it as an unrecoverable failure.


On Tue, May 15, 2018 at 7:31 AM Chris Hegarty <chris.hegarty at oracle.com>
wrote:

> Simon,
>
> > On 15 May 2018, at 14:25, Simon Roberts <simon at dancingcloudservices.com>
> wrote:
> >
> > ...
> > I'm running on Linux, not Mac, and t's just a thrown together node.js
> server. I guess that means the real bug is probably in node, though one
> would think that the Java implementation should be robust enough to at
> least not crash (
>
> To be clear, this is NOT a crash ( in Java terms ).
>
> The exception, " java.io.EOFException: EOF reached while reading”,
> that you are seeing is conveying the message that and unexpected
> end-of-file(stream) has been reached while received data. This
> appears to be correct as per Joacim’s observation.
>
> Silently ignoring, or otherwise not reporting, the unexpected EOF,
> would be incorrect and considered a bug.
>
> -Chris.



-- 
Simon Roberts
(303) 249 3613
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openjdk.java.net/pipermail/net-dev/attachments/20180515/dcae35ed/attachment.html>