A coworker is using some <cfthread...> tags to do some fire and forget asynchronous processing of PDF document creation. The <cfthread...> code creates a PDF file and writes it to a directory and is done. This works well in small scale testing and each iteration takes less then a second to run. But when we run the full process that needs to generate ~1300 files, the server is brought to its knees and we start getting Java out-of-memory errors.
Before we just upped available memory to the JVM, which we probably should do, we wanted some metrics to see what was really happening first. Using the CF 8 server monitor we see these threads generated by this code and they never go away. Every time we run a test of the application more threads are added, more memory is used by ColdFusion|JVM. What should we be doing to expire these threads when their work is done, or in someway make sure these resources are reclaimed and available for future use. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to date Get the Free Trial http://ad.doubleclick.net/clk;192386516;25150098;k Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:307240 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
