This is a general Java question, although it might (possibly) point to a bug in the v5 port or in 1.1.6 itself. Under what circumstances does PipedInputStream.read() or PipedOutputStream.write() throw an IOException for "Pipe broken?" Intuitively, what I think should happen is that a pipe throws an IOException if either (a) it hasn't been connected to another pipe, (b) close() was called on the pipe it had been connected to, or (c) finalize() ran on the pipe it had been connected to. However, I'm getting a "Pipe broken" IOException even though the pipe is connected to another pipe and neither close() nor finalize() has been run on either the input pipe or the output pipe. *If* what I just described were true, would it be a bug in Java, or am I misunderstanding the cases when "Pipe broken" is thrown? Thanks very much for your help; this problem is causing a nasty bug just prior to release. Best, daniel dulitz Valley Technologies, Inc. Peak Performance Real-Time DSP State College, PA
