Dan G. Switzer, II wrote: > Ian, > I wonder if the problem isn't with <cfthread /> but actually with heavy > usage of either <cfreport /> or <cfpdf /> tags. > > Are you creating large reports? It could be a memory issue your running in > to. How much RAM is available to the JVM? > > I would try simplifying things. Does it always work if you comment out the > <cfreport /> and <cfpdf /> tags? > > If it does, what happens if you comment out the <cfreport /> tag and just > write a very simply PDF? > > I could see how if you're generating some large PDFs, that without enough > RAM it could drive the JVM nuts. > > -Dan
The memory usage of the PDF report generation is defiantly a problem. It is what we where trying to address with the usage of the thread tag. The idea being that by splitting the process into separate threads and throttle them down would allow the server time to clean up memory used in previous iterations. That is a topic for a seperate discussion. How does <cfreport...> work in large iterations. We found that no matter what we did, the memory used by the report tag would just climb and climb each iteration unless we broke up the process into completely separate HTTP requests. By creating a template that would process a small number of reports per request and then send a page to the browser with a META refresh to re-request the page in one second. This works fine. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to date Get the Free Trial http://ad.doubleclick.net/clk;203748912;27390454;j Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:308857 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
