Hmmm...there is a distinct lack of named locks around some cffile calls
in a scheduled task. (Not my code.) A possible culprit?

The other difficulty here is that this was not happening until after
some access changes had been made to allow a directory to be accessed by
an anonymous web user for a scheduled task. There's nothing really that
exotic going on.



-----Original Message-----
From: Dave Watts 
Sent: Friday, August 18, 2006 12:48 PM
To: CF-Talk
Subject: RE: CF bringing down IIS Application Pool

> Got a scenario I'm currently investigating. Our test and production 
> machines are crapping out on a daily basis. It appears that something 
> ColdFusion is doing is bringing down the IIS application pool. Oddly, 
> the identically-configured development server is unaffected.
>  
> What would cause that to happen? A runaway memory leak?

The only part of CF that runs within the IIS application pool is the
ISAPI filter and/or extension that is installed by the web server
configuration utility. Generally, all that does is pass requests to the
CF server, but I believe that it handles a more significant part of file
uploads via CFFILE and downloads via CFCONTENT, so I'd look at those
first.

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!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting,
up-to-date ColdFusion information by your peers, delivered to your door four 
times a year.
http://www.fusionauthority.com/quarterly

Archive: 
http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:250308
Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm
Unsubscribe: 
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4

Reply via email to