JCraft, SSH and System.in

Question

Hello,
I'm currently trying to use Jsch package from JCraft.
I'm trying to send a series of command to a distant computer through SSH.
As there is absolutely no forum, wiki or tutorial for this package, I'm ending up here.
I adapted the Shell.java example given on the Jsch Website. I only changed the input and outputStream used for the SSH dialog.
I must had that when I replace the output and input stream by System.in and System.out as it is the case in the example given, my program works fine.
But when I use my own Streams, every thing works fine for the OutputStream but things are going wrong with the input stream.
I produced an inputStream of my own extending java.io.InputStream.
According to what I found out, the Jsch.channel does read inside my inputStream so he must obtain exactly the same thing as if it came from System.in.
Is there something specific done by System.in that make it different from the return of any other inputStream ?
Can someone help me ?
Here is the code of my inputStream :
package com.omniris.io;
public class InputStream
     extends java.io.InputStream
     private int[]      toWrite      = new int[2048];
     private int      bufferLength     = 0;
     public InputStream()
          super();
     public int available()
          return bufferLength;
     public int read()
          throws java.io.IOException
          int toReturn=0;
          while ( (available()<=0) || ( (available()>0) && (toWrite[available()-1]!=10)) )
          System.out.println("Caractère lu :"+((char)toWrite[0]) + " : "+toWrite[0]);
          toReturn = toWrite[0];
          decaler();
          return toReturn;
     public void write(String command)
          int depart = available();
          byte[] toAdd = command.getBytes();
          for (int x = 0 ; x<toAdd.length ; x++)
               toWrite[depart+x] = toAdd[x];
               bufferLength++;
     public void decaler()
          int fin = available();
          for(int x = 1 ; x < fin ; x++)
               toWrite[x-1] = toWrite[x];
          toWrite[fin-1] = 0;
          bufferLength--;
     }

Answer 1

There may be a better way but it seems that one has to use piped streams and threads to handle this -        final Channel channel = session.openChannel("shell");
        final PipedOutputStream pos = new PipedOutputStream();
        channel.setInputStream(new PipedInputStream(pos));
        new Thread(new Runnable()
            // Use whatever character encoding your remote machine uses
            private final BufferedWriter br = new BufferedWriter(new OutputStreamWriter(pos, "utf-8"));
            public void writeCommand(String command) throws IOException
                br.write(command);
                br.write("\n");
                br.flush();
            public void run()
                try
                    writeCommand("/bin/ls");
                    writeCommand("ps -elf");
                    writeCommand("uname -r");
                    writeCommand("exit");
                } catch (IOException e)
                    e.printStackTrace();
        }).start();
        final PipedInputStream pis = new PipedInputStream();
        channel.setOutputStream(new PipedOutputStream(pis));
        new Thread(new Runnable()
            // Use whatever character encoding your remote machine uses
            private final BufferedReader br = new BufferedReader(new InputStreamReader(pis, "utf-8"));
            public void run()
                try
                    for (String line = null; (line = br.readLine()) != null;)
                        System.out.println("Line:" + line);
                    // Write these lines to your Swing component making sure you
                    // update in the event dispatch thread using SwingUtitlities.invokeLater()
                } catch (Exception e)
                    e.printStackTrace();
                } finally
                    session.disconnect();
                    final int exitStatus = channel.getExitStatus();
                    System.out.println("Exit status : " + exitStatus);
        }).start();Edited by: sabre150 on Jan 13, 2009 2:40 PM
Updated code to better handle 'exit' .