> I'd try to really limit the number of threads your creating. > I'd even look at limiting things to a fixed number of worker > threads. Try dividing the work load between like 5 or 6 > threads. Have each thread process it's share of the work load > (i.e. each work load would handle 1/5 of the workload--so > w/500 records, thread one would work on records 1-100, thread > 2 would work on records 101-200, etc.)
Dan and Brad's suggestions are the way to go here. With 1K concurrent threads, I'm surprised it's not failing even quicker. One common pattern of sorts to use here is to create a thread pool and a controller thread. The controller thread could keep track of which reports have and/or haven't been generated, and track the progress of the worker threads. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ Fig Leaf Software provides the highest caliber vendor-authorized instruction at our training centers in Washington DC, Atlanta, Chicago, Baltimore, Northern Virginia, or on-site at your location. Visit http://training.figleaf.com/ for more information! ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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:308911 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
