Malformed JSON: java.io.IOException: Pipe broken

[ianparkinson]

Occasionally, helog fails with:

Malformed JSON: java.io.IOException: Pipe broken

(Or, when --raw is specified, just Pipe broken)

I've only noticed this when multiple instances of helog are running, and they all fail at the same time.

[ianparkinson]

helog uses a PipedReader/PipedWriter pair to conveniently shepherd text from the WebSocket.Listener to a separate thread running gson.fromJson() (which blocks).

According to javadoc for the related PipedInputStream:

A pipe is said to be broken if a thread that was providing data bytes to the connected piped output stream is no longer alive.

...and I can see in the source for PipedReader that, on read, it checks whether the last thread that wrote to the PipedWriter is still alive, and fails with Pipe broken if not. Meanwhile WebSocket doesn't guarantee that it will always call the listener using the same thread (and nor should it).

That doesn't entirely explain why multiple runs all fail simultaneously, but presumably there's some OS-level socket dispatching going on.