> CFSERVER on win2k isn't run as an ISAPI filter afaik. Its > called as a DLL, but process execution opperates under the > Cold Fusion processes.
You're correct that CFSERVER itself isn't run as an ISAPI filter or extension. However, CF receives requests from IIS through an ISAPI filter or extension. With CF 5, IIS communicates with CF through the ISAPI extension \CFusion\bin\ISCF.DLL. With CFMX, IIS communicates with CF through \CFusionMX\runtime\lib\wsconfig\n\jrun.dll (where "n" is the number corresponding to the order in which CFMX was configured to talk to IIS - for example, if you configure Apache to talk to CFMX first, then later configure IIS to talk to CFMX, "n" would be 2). With CFMX, the DLL can be configured as either an ISAPI extension or filter. > I can say with a fairly monsterous ammount of confidance > that on win2k with cf4.0/5.0/MX DLLHOST processes are > typically not associated with Cold Fusion consumption. If the IIS application settings for a specific virtual server are set to "Medium" or "High", and the ISAPI extension is doing a lot of work (handling CFCONTENT requests is the only thing I can think of offhand), then you may see significant resource consumption by DLLHOST.EXE. If the IIS application settings for a specific virtual server are set to "Low", and the ISAPI extension is doing a lot of work, then you may see significant resource consumption by INETINFO instead. > If you're running CF as an ISAPI filter through some stretch > I'm not aware of? I'd probably reccomend against it given how > ISAPI filters behave. Just a default install tiein with CF > and win2k thought will not be running through the DLLHOSTS. CF 5 doesn't let you use an ISAPI filter, only an extension. CFMX lets you use either one. To be honest, I'm not sure what it uses as the default, as I haven't yet let CFMX do a default web server configuration during install. As for Win2K, I'm not sure what the default settings for application isolation in IIS are; I thought it used "Medium", in which case it would use DLLHOST.EXE to run ISCF.DLL. At any rate, when I configure a server, I always make sure it's set to "Low". > I'd suspect if your DLLHOSTS are consuming ASP resources out > of hand, you probably need to check into your ASP > applications rather then CF. Most of the servers I've worked with have only been running CF applications - and typically, only one of those. I've seen the DLLHOST.EXE thing a couple of times under those circumstances. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ voice: (202) 797-5496 fax: (202) 797-5444 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq This list and all House of Fusion resources hosted by CFHosting.com. The place for dependable ColdFusion Hosting. Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
