Re: broken pipe
On 18 Jan 2007 11:13:39 -0800, norberthauser04@web.de wrote:
As to your suggestions on listen(), I changed the "new Thread()" calls
as follows:
--- source fragment ---
new Thread(){
public void run(){
try {
String line;
while(true){
line = in.readLine();
if (line!=null)
System.out.println("STD: "+line);
else {
System.out.println("STD: READ NULL"); // for
debug only
sleep(2000);
}
}
} catch (IOException e){ System.err.println(e);}
catch (InterruptedException e){ System.err.println(e);}
}
}.start();
--- end ---
Reading null from the input stream indicates that you have reached the
*end* of the stream, i.e. that the remote has closed his end of the
stream or exited. Once that occurs, you will never be able to read
anything but null, so there is little point in sleeping and continuing
the loop. Your loop should look something like this:
while ((line = in.readLine()) != null) {
System.out.println(line);
}
After leaving this loop, you should realize that the process is likely
gone and will be unable to accept more commands. As you've indicated
in another post, ps no longer shows the process at this point.
Does this output give any new insight on what might be happening, or
can you imagine why 4bol remains active in the terminal but closes it's
input pipe in the java program?
Many programs detect that they are not in a terminal and intentionally
behave differently. You can test this by creating a text file with
sample input commands, and running the program (from a shell) like
this:
4bol < input.txt > output.txt
Probably it will exit when it encounters parse errors, just like it
does when you run it from Java.
If that's the case, then your Java program should simply detect that
it has exited, restart it, and set up new listeners.
/gordon
--
[ don't email me support questions or followups ]
g o r d o n + n e w s @ b a l d e r 1 3 . s e