WaitFor() works only when in debugging mode!

Question

Hi, im having a problem with making my function waits for a process to end while in run mode!
The function always run and exists while the process is still running...
I checked it in debugging mode and it worked just fine, but i cant seem to be able to make it work in the run mode!
Any hints???
Here is my code:
public void executeBatch (){
try{
Runtime runtime = Runtime.getRuntime();
Process batchProcess = runtime.exec(new String[] {"cmd.exe", "/c", "FetchFiles.bat"}, null, new File(BATCH_FILES_PATH));
BufferedReader b = new BufferedReader(new InputStreamReader(batchProcess.getErrorStream()));
if (b.ready()){
String line=null;
while ( (line = b.readLine()) != null) {
System.out.println(line);
line = b.readLine();
int exitVal = batchProcess.waitFor();
System.out.println("Exit Value = " + exitVal);
} else {
b = new BufferedReader(new InputStreamReader(batchProcess.getInputStream()));
if (b.ready()){
String line=null;
while ( (line = b.readLine()) != null) {
System.out.println(line);
line = b.readLine();
int exitVal = batchProcess.waitFor();
System.out.println("Exit Value = " + exitVal);
} catch ( Exception ex ){
System.out.println("executeBatch : " + ex.getMessage());
btw, the process is a batch that connects to a linux server and "mget" files from some directories in the server...

Answer 1

what the ....???
the "BadExecWinDir.java" bad approach is all about
not using an executable command like "dir"... which
im not using at all...More than that but secondary.
>
and for the "GoodWindowsExec.java" concept
demonstrates that you should handle the standard
error and standard input streams and emptying them
both together, which what i exactly did. i USED the
concept...
My piece of code is the same as the
"GoodWindowsExec.java" code except that i made the
code of the StreamGobbler class comes inside the
function directly, and that i didn't use a checkup on
the operating system to decide wither it's a Windows
NT or Windows 95 to decide the command prompt
executable name...StreamGobbler runs as a thread so both streams are emptied in parallel. In your code
           String line=null;
            while ( (line = brError.readLine()) != null)
                System.out.println(line);this will only terminate when the process terminates and closes stderr. This means that the following code
          while ( (line = brInput.readLine()) != null)
                System.out.println(line);
            only starts to run once the process terminates.
BUT, the stderr stream and stdout streams have a limited buffer and block when this buffer becomes full. So, if the stdout stream produces more than a buffer full then it blocks until more room is avaialable and the process cannot terminate so the error stream cannot be closed so the code to empty stdout cannot run to make room in the buffer to put more output. Phew!
If you change the order of emptying the two streams then you have a simillar effect.
The only way I know of dealing with this is to empty both streams at the same time so you need two threads. You can use the default thread for one but you MUST use another thread for the other. Since I use stdout, stderr and stdin I use 3 threads!
>
thats all...Please read the article again.