Search the Macromedia knowledge base, I think there's information there about CF admin settings. Also, search on information about how CF handles threads.
You need to find why your .cfm templates are running so slowly - that's what's killing you. It sounds like the "restart at X number of unresponsive threads" is set too low. Generally that should be 80% of the number of threads. The number of threads should be about 3 to 5 per processor. The CFadmin default setting makes the restart number greater than the total number of threads, so CF never restarts even if all threads are unresponsive. Chris Norloff ---------- Original Message ---------------------------------- from: "Smith, Matthew P -CONT(DYN)" <[EMAIL PROTECTED]> Reply-To: [EMAIL PROTECTED] date: Wed, 28 Aug 2002 10:30:22 -0500 >I am having a problem with unresponsive threads crashing the server. It >seems that they are not being released even after they exceed the timeout >specified in cf administrator(90 seconds). > >It took over 37 minutes for the same template to generate unresponsive >threads. Why doesn't CF drop them when they exceed the time limit? > >"Information","238","08/28/02","05:52:49",,"The ColdFusion Application >Server started." >"Warning","88","08/28/02","06:53:12",,"Template: >D:\Inetpub\wwwroot\webServices\deersValidation.cfm, Ran: 101 seconds." >"Warning","304","08/28/02","06:53:13",,"Template: >D:\Inetpub\wwwroot\foo\dverify.cfm, Ran: 102 seconds." >"Warning","426","08/28/02","07:06:19",,"A request exceeded the timeout. The >unresponsive thread count is up to 1. [D:\Inetpub\wwwroot\foo\dverify.cfm]" >"Error","426","08/28/02","07:06:19",," !! CFTrace::logThread(304) has no >entry for thread 304" >"Warning","426","08/28/02","07:12:19",,"A request exceeded the timeout. The >unresponsive thread count is up to 2. >[D:\Inetpub\wwwroot\Cantrac\dverify.cfm]" >"Error","426","08/28/02","07:12:19",," !! CFTrace::logThread(324) has no >entry for thread 324" >"Warning","426","08/28/02","07:16:49",,"A request exceeded the timeout. The >unresponsive thread count is up to 3. [D:\Inetpub\wwwroot\foo\dverify.cfm]" >"Error","426","08/28/02","07:16:49",," !! CFTrace::logThread(88) has no >entry for thread 88" >"Warning","426","08/28/02","07:18:19",,"A request exceeded the timeout. The >unresponsive thread count is up to 4. [D:\Inetpub\wwwroot\foo\dverify.cfm]" >"Error","426","08/28/02","07:18:19",," !! CFTrace::logThread(464) has no >entry for thread 464" >"Warning","426","08/28/02","07:21:19",,"A request exceeded the timeout. The >unresponsive thread count is up to 5. >[D:\Inetpub\wwwroot\Cantrac\dverify.cfm]" >"Error","426","08/28/02","07:21:19",," !! CFTrace::logThread(327) has no >entry for thread 327" >"Warning","426","08/28/02","07:43:49",,"A request exceeded the timeout. The >unresponsive thread count is up to 6. [D:\Inetpub\wwwroot\foo\dverify.cfm]" >"Error","426","08/28/02","07:43:49",," !! CFTrace::logThread(568) has no >entry for thread 568" >"Warning","426","08/28/02","07:55:49",,"A request exceeded the timeout. The >unresponsive thread count is up to 7. >[D:\Inetpub\wwwroot\Cantrac\dverify.cfm]" >"Error","426","08/28/02","07:55:49",," !! CFTrace::logThread(129) has no >entry for thread 129" >"Warning","554","08/28/02","07:56:44",,"Template: >D:\Inetpub\wwwroot\webServices\deersValidation.cfm, Ran: 210 seconds." >"Information","129","08/28/02","07:56:45",,"A long-running request returned. >The unresponsive thread count is down to 6. >[D:\Inetpub\wwwroot\foo\dverify.cfm]." >"Warning","129","08/28/02","07:56:45",,"Template: >D:\Inetpub\wwwroot\foo\dverify.cfm, Ran: 211 seconds." >"Warning","426","08/28/02","08:00:19",,"A request exceeded the timeout. The >unresponsive thread count is up to 7. [D:\Inetpub\wwwroot\foo\dverify.cfm]" >"Error","426","08/28/02","08:00:19",," !! CFTrace::logThread(308) has no >entry for thread 308" >"Warning","426","08/28/02","08:04:49",,"A request exceeded the timeout. The >unresponsive thread count is up to 8. [D:\Inetpub\wwwroot\foo\dverify.cfm]" >"Error","426","08/28/02","08:04:49",," !! CFTrace::logThread(554) has no >entry for thread 554" >"Warning","426","08/28/02","08:07:49",,"A request exceeded the timeout. The >unresponsive thread count is up to 9. [D:\Inetpub\wwwroot\foo\dverify.cfm]" >"Error","426","08/28/02","08:07:49",," !! CFTrace::logThread(129) has no >entry for thread 129" >"Fatal","426","08/28/02","08:09:19",,"Unresponsive thread threshold reached. >Restarting service." >"Information","177","08/28/02","08:09:23",,"The ColdFusion Application >Server started." >(ETC) > > > >The template uses a custom tag call that does a cfhttp call to another >template on the same server, trying my hand at a pseudo web service. > >Basically: >1. Template calls custom tag for validation. >2. Custom tag calls (local/same cf server) web service url >3. Web service url/template checks if local cache(ms sql db) if user >validation expired. If not expired and validates properly, returns "1". >4. If expired: > Calls a third party web service, which we validate against. > Validation fails, return "0" > Validation succeeds, insert to local db cache, return "1" > >I hope that makes sense. > >Could that cause problems? I would guess that it would take two threads as >one template calls another... But that shouldn't be to bad. > >We've tried tweaking cf administrator a bit, but we're not really sure which >setting to play with. > >Thanks for any help. > ______________________________________________________________________ Signup for the Fusion Authority news alert and keep up with the latest news in ColdFusion and related topics. http://www.fusionauthority.com/signup.cfm FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
