I have a process that generates flat files using CFFILE. The
process uses a database reference table that feeds the query
parameters. I have several loops in this process which I thought
would be more efficient and free up memory after each CFFILE
"action append" but before execution of the next query. (execute
query then write all the files, loop to query then write all files,
etc....)
Problem is that it is not freeing up memory and I am getting
java.lang.OutOfMemoryError errors after about 15 minutes of run
time.
Current solution is to run this process in batches. This
unfortuantly requires someone baby sit the process and change a
parameter and submit.
Is there anyway after the one of the loops is complete (query
has completed and first group of files have been written) and
before the next execution of the query that I can free memory?
I need to trick the process in thinking that the page is
complete then immediately initiate the next query to process the
files.
We have tuned the box as best we can, applied all patches
(MX7) . Process runs great in batches, but, just can't handle the
volume. Millions of rows are being processed.
Thanks
Bill