File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
The moose likes Java in General and the fly likes too many open files - together with ProcessBuilder Big Moose Saloon
  Search | Java FAQ | Recent Topics
Register / Login


Win a copy of Mongo DB Applied Patterns this week in the MongoDB forum
or a resume review from Five Year Itch in the Jobs Discussion forum!
JavaRanch » Java Forums » Java » Java in General
Reply Bookmark "too many open files - together with ProcessBuilder" Watch "too many open files - together with ProcessBuilder" New topic
Author

too many open files - together with ProcessBuilder

Reinhard Mantey
Greenhorn

Joined: Jan 09, 2010
Posts: 6
Hello,

I'm going to process a bunch of files (few thousands) and I call external tools for that.
The places where I open a file for reading or writing, I use close in the finally section.

I also use close on the InputReader, I use for getting the output from the called tool.

How can I find out, what breaks my code?
Do I need to call gc or something else?

Are there side-effects of the ProcessBuilder, that I did not cared about?

Any hint is appreciated.

kind regards
Reinhard
William Brogden
Author and all-around good cowpoke
Rancher

Joined: Mar 22, 2000
Posts: 12265
    
    1
If you are exec()ing the "external tools" then it may be that you are not consuming the stdErr output of the Process.

As I understand it, a stdErr output stream is always created - perhaps that is showing up as an open file?

In any case, carefully read the java.lang.Process JavaDocs.

Bill

Java Resources at www.wbrogden.com
 
I agree. Here's the link: jrebel
 
subject: too many open files - together with ProcessBuilder
 
Similar Threads
SFTP from java
help using runtime.exec
Calling Perl from Java
Variable number method parameters determined by .ini file
GC