Cflocation within a scheduled task would be the first thing I'd toss while testing. Doesn't sit well with me.
I'd replace it with a CFHTTP call (you're generating a url already) and if I really wanted to decouple the two I may put it in a CFTHREAD. Just some testing ideas. - Gabriel On Tue, Mar 9, 2010 at 3:53 PM, Bryan S <[email protected]> wrote: > > So today's work narrows things down even further. > > The Cold Fusion Scheduled Task calls Event1. > > Event1 constructs a URL and passes it to a .cfm which uses a cflocation to > fire the URL. > > The fired URL calls Event2 that starts a report. > > I pass an identifier through from the the URL called by the Cold Fusion > Scheduled Task (Event1) all the way through to the URL fired by the > cflocation (Event2). > > Five minutes later the exact same URL is fired again. There is not a second > call to Event1. The Cold Fusion Scheduled Task (Event1) does not get called > again. > > Nothing happens until both reports are finished and then the process is > repeated. > > Bryan > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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:331495 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
