Process implementation

Question

I'm creating a process like this.:
Process proc = null;
try {
Runtime rt = Runtime.getRuntime();
     try{
     proc = rt.exec("cmd /c dir");
     catch(SecurityException e){
          System.out.println("SecurityException!");
     catch(IOException e){
          System.out.println("IOException!");
     catch(NullPointerException e){
          System.out.println("NullPointerException!");
     catch(IllegalArgumentException e){
          System.out.println("IllegalArgumentException!");
     if (proc!=null){
          proc.waitFor();
} finally {
if (proc != null) {
proc.destroy();
So , the problem is:
-the handles for proc , for the input , output and err files associated with the process are not closed.So the destroy method doesn't do anything.
If i'm closing the input,output and err files associated with the process like this:
finally{
//add this
InputStream in = proc.getInputStream();
OutputStream out = proc.getOutputStream();
InputStream err = proc.getErrorStream();
The handles associated with in,out and err are closed(like expected) .
But the question is: How can i close the handle of the process.
Thanks.
I'm asking all this question because at I get the message "Too many open files"(on a java project on HP-UX)- When this message is written to the logs, it indicates that all available file handles for the process have been used. In a majority of cases, this is the result of file handles being leaked by some part of the application. This technote explains how to collect output that identifies what file handles are in use at the time of the error condition - taken from ibm docs.

Answer 1

sorinL wrote:
Thanks ,I have read the doc . Hard :d . But there is no util information about releasing all the resources(handles).I suspect that if you implement the recommendations then you won't need to release the resources. I have never ever had to release file handles working on Linux, Solaris and Windows XP.
Your call.
P.S. Please fix that exception handling.