On Mar 16, 6:19 pm, javama...@gmail.com wrote:

Perhaps in 2003.  Which in computer terms is like
'dog years' - that is, 1 for 7, which would make it..
'1973' as far as any current day programmer remembers.

Use a current version of tomcat.  It may not
fix the problem, but at least people might
care enough to investigate the root cause.  ;-)

--
Andrew T.
PhySci.org

Does "program.exe" (with the long wait time) work on the command line, or  
when launched outside of your code? If not, you probably will not be able  
to solve the problem within the VM.

Also, what do you mean by "the results give a paging file error"? Does the  
VM crash? The launched process? Both? How much RAM does the process need?  
Do you have enough while the VM is running? Does the error occur before  
the process is launched, shortly after, or a noticeable while after?

Hhow much output does the program write to the console? Be sure you are  
reading Process.getErrorStream() & Process.getInputStream() and keeping  
those streams drained so the OS doesn't have to continuously buffer the  
process output. You might be able to get away with calling

p.getErrorStream().close();
p.getInputStream().close();

But if something goes wrong, you've swallowed your best debugging  
information, so this is probably best avoided.

HTH,

-Zig

The most likely reason for a Paging File Error is that you have exceeded the
maximum amount of virtual memory in the system. That is the sum of the virtual
memory requirements of all processes has exceeded the sum of the physical RAM
plus maximum paging file size.

I doubt very much that it has anything whatever to do with the "wait time", but
is entirely due to the "processing large files".

Buy more RAM, increase the paging file size, or get a better OS.