You could dynamically name the lock to use the same name (only one report runs at once) or use a unique name (allow multiples to run). Still, mitigation, not a fix.
I think the lack of responses is because this may be tightly coupled to your implementation and is not general enough for constructive responses. I don't think you're doing anything wrong but it may be that you're problem is too specific to you. Maybe someone will have a Eureka moment. :) - Gabriel On Tue, Mar 9, 2010 at 8:51 AM, Bryan S <bryansgroup...@gmail.com> wrote: > > Thanks a lot for the reply. I simplified my explanation to get right to the > point. There are times when I want multiple reports to run at once. Event1 > actually checks if a large memory hogging report is running. If not it fires > Event2 even if another report is running. > > Bryan > > -----Original Message----- > From: Dorioo [mailto:dor...@gmail.com] > Sent: Tuesday, March 09, 2010 8:41 AM > To: cf-talk > Subject: Re: Phantom Scheduled Tasks > > > Can't speak to the cause from afar. But to prevent reports from > running concurrently, maybe you can put a named CFLOCK around all of > the report generation events. If they all shared the same name, only > one would ever have the lock and, if a second started to run while the > first was running, it would simply time out and not do anything. > Something like this post: > > http://www.bennadel.com/blog/1844-Making-Sure-Scheduled-Tasks-Don-t-Overlap- > In-ColdFusion.htm > > It's not a fix but it would mitigate multiple report events running > concurrently. > > - Gabriel > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Want to reach the ColdFusion community with something they want? Let them know on the House of Fusion mailing lists Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:331465 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
