今天搞了一天，JAVA調用一個PERL程序，得不得就退不出，千試萬試，LOG精細到逐行，知道在哪停住了，但打死不知道為什么。
后來吃個飯都放棄了，居然又找到答案，要沒看到它，那真以為里面有鬼了。

大概原因是，調用Runtime.getRuntime().exec后，如果不及時捕捉進程的輸出，會導致JAVA掛住，看似被調用進程沒退出。所以，解決辦法是，啟動進程后，再啟動兩個JAVA線程及時的把被調用進程的輸出截獲。

一下子，整個世界清爽多了。。。多謝這么仁兄，下面轉一下：



轉自：http://pudding.sharera.com/blog/BlogTopic/31232.htm

碰到一個項目需要從Java中運行Perl程序，這個Perl程序調用客戶的Web service，每次發送一個請求，接受一個響應。Java程序中包含多個請求，需要多次調用Perl程序，并且接受和解析響應（這個爛設計可不是我干 的，我實在不明白強大的Java Web Service為什么要弄成這樣，不過客戶是老大）。使用Java Runtime的exec()方法，發現運行一段時間后，進程就被掛起了（之前的響應完全正確）。于是分析原因，發現我在運行exec()方法后，立刻執 行了Process的waitFor()方法，這里出了問題。在網上找到一篇文章講述這個問題：
地址：http://brian.pontarelli.com/2005/11/11/java-runtime-exec-can-hang/

Java Runtime exec can hang

November 11, 2005 on 4:40 pm | In Java |

The next version of Savant is going to focus heavily on the stand-alone runtime anｄ support for dialects anｄ plugins. Supporting all that is largely handled by using a simple executor framework I wrote around Java 1.4 anｄ lower’s Runtime.exec method. A few things to keep in mind when using this:

1. Always read from the streams prior to calling waitFor. Otherwise you could end up waiting forever on Windows anｄ other OS platforms whose I/O buffers can’t store enough from standard out anｄ standard error to ensure the program has finished. These platforms will pause the execution of whatever is running until something reads the buffered content from standard out anｄ standard error. I would imagine all platforms suffer from this, but some platforms have larger buffers than others. Needless to say, always read from the streams first.
2. Always read from standard error first. I ran across a bug where some OS platforms will always open standard out, but never close it. What this means is that if you read from standard out first anｄ the process only writes to standard error, you’ll hang forever waiting to read. If you read from standard error first, you’ll always be okay on these platforms because the OS seems to shutdown standard error. I think however, that the best way to handle all cases is to check both standard error anｄ standard out for readiness anｄ only read from them if they have something to offer. The downside I could see here is that error isn’t ready, but eventually will be.

可以看出：

• 永遠要在調用waitFor()方法之前讀取數據流
• 永遠要先從標準錯誤流中讀取，然后再讀取標準輸出流

于是將waitFor()方法放在讀取數據流后調用，目前沒有發現什么問題。

正好解決了我心中的疑問，非常感謝！

我們的程序一開始就是exec完了接著waitFor()，但bat文件執行不完整：

Process proc = Runtime.getRuntime().exec(cmd);
                proc.waitFor();

后面的build中在waitFor()之前讀取了數據流，bat文件就可以完整執行了：

Process proc = Runtime.getRuntime().exec(cmd);
     StreamGobbler errorGobbler = new StreamGobbler(proc.getErrorStream(), "Error");           
                 StreamGobbler outputGobbler = new StreamGobbler(proc.getInputStream(), "Output");
                 errorGobbler.start();
                 outputGobbler.start();

     proc.waitFor();

class StreamGobbler extends Thread {
 InputStream is;

 String type;

 StreamGobbler(InputStream is, String type) {
  this.is = is;
  this.type = type;
 }

 public void run() {
  try {
   InputStreamReader isr = new InputStreamReader(is);
   BufferedReader br = new BufferedReader(isr);
   String line = null;
   while ((line = br.readLine()) != null) {
    if (type.equals("Error"))
     LogManager.logError(line);
    else
     LogManager.logDebug(line);
   }
  } catch (IOException ioe) {
   ioe.printStackTrace();
  }
 }
}

TestPrint.bat:

echo P1=%1  >D:"2.1.2env"2.1.2home"CompuSet"output"TestPrint.log
echo P2=%2 >>D:"2.1.2env"2.1.2home"CompuSet"output"TestPrint.log
echo P3=%3 >>D:"2.1.2env"2.1.2home"CompuSet"output"TestPrint.log
echo P4=%4 >>D:"2.1.2env"2.1.2home"CompuSet"output"TestPrint.log
echo P5=%5 >>D:"2.1.2env"2.1.2home"CompuSet"output"TestPrint.log
echo P6=%6 >>D:"2.1.2env"2.1.2home"CompuSet"output"TestPrint.log

Bad_TestPrint.log:

P1=C:"xPression"CompuSet"output"MartyTestOut1.afp 
P2=Literal1
P3="Rick Skinner"
P4=Parameter3

Good_TestPrint.log

P1=C:"xPression"CompuSet"output"MartyTestOut1.afp 
P2=Literal1
P3="Rick Skinner"
P4=Parameter3
P5=Parameter4
P6=Parameter5