Piped streams, data lines and threads - what's the bug?

Question

Please, help!
What is wrong here and what should I do to make it running?
Strictly speaking, one thread becomes blocked (in) and another runs in a short circuit (out).
The code is:
    TargetDataLine stdin;
    SourceDataLine stdout;
    PipedInputStream pipein;
    PipedOutputStream pipeout;
    public void pipeDirectly() throws Exception {
        stdin = AudioSystem.getTargetDataLine(DEFAULT_FORMAT);
        stdout = AudioSystem.getSourceDataLine(DEFAULT_FORMAT);
        pipein = new PipedInputStream();
        pipeout = new PipedOutputStream(pipein);
        stdin.open(DEFAULT_FORMAT, 16384);
        stdout.open(DEFAULT_FORMAT, 16384);
        stdin.start();
        stdout.start();
        Thread in = new Thread() {
            public void run() {
                try {
                    byte[] buffer = new byte[100000];
                    while (true) {
                        int avl = stdin.available();
                        if (avl > 0) {
                            stdin.read(buffer, 0, avl);
                            pipeout.write(buffer, 0, avl);
                } catch (Exception ex) {
                    ex.printStackTrace();
                    throw new RuntimeException(ex);
        Thread out = new Thread() {
            public void run() {
                try {
                    byte[] buffer = new byte[100000];
                    while (true) {
                        int pipeAvl = pipein.available();
                        int outAvl = stdout.available();
                        int avl = Math.min(pipeAvl, outAvl);
                        if (avl > 0) {
                            int read = pipein.read(buffer, 0, avl);
                            stdout.write(buffer, 0, read);
                } catch (Exception ex) {
                    ex.printStackTrace();
                    throw new RuntimeException(ex);
        out.start();
        in.start();
        in.join();
    }Thank you!

Answer 1

Actually, tried.
There were one or two passes of "in" thread and repeating pipeAvl=0 in "out".
I have watched the thread state (IDE debugger) and realized that these things were called inside "in" thread:
wait():-1; java.lang.Object
awaitSpace():204; java.io.PipedInputStream
receive():161; java.io.PipedOutputStream
write(): 129; java.io.PipedOutputStream
run(): <my method location>
the numbers are actually the number of line from source. -1 is for native method.
Why it behaves like this? I don't understand.
To compare, this code works almost beautifully:
    TargetDataLine stdin;
    SourceDataLine stdout;
    PipedInputStream pipein;
    PipedOutputStream pipeout;
    public void pipeDirectly() throws Exception {
        stdin = AudioSystem.getTargetDataLine(DEFAULT_FORMAT);
        stdout = AudioSystem.getSourceDataLine(DEFAULT_FORMAT);
        pipein = new PipedInputStream();
        pipeout = new PipedOutputStream(pipein);
        Thread in = new Thread() {
            public void run() {
                try {
                    stdin.open(DEFAULT_FORMAT, 16384);
                    stdout.open(DEFAULT_FORMAT, 16384);
                    stdin.start();
                    stdout.start();
                    byte[] buf = new byte[100000];
                    while (true) {
                        int avl = stdin.available();
                        stdin.read(buf, 0, avl);
                        stdout.write(buf, 0, avl);
                } catch (Exception ex) {
                    throw new RuntimeException(ex);
        in.start();
        in.join();
    }Message was edited by:
MaxBuzz