ooooppps! RE 2) restarting IIS is independant of the CF process, unless you chanegd that dependemcy of course.
>-----Original Message----- >From: Ye Wang [mailto:[EMAIL PROTECTED]] >Sent: Thursday, February 06, 2003 2:31 PM >To: CF-Talk >Subject: Re: why does CF Server times out so often? > > >Doug, > >Thanks for your reply. > >> 1) are you using ODBC connections to Access? This used to >be an issue of >the ODBC driver fouling the works up. We had to >> schedule the CF service to bounce every. All was fine after that. > >We've been using SQL 2000, not Access. How do you schedule >cuff server to >bounce? > >> 2) in the Cadman tool, make sure 'restart after n >unreponsive requests' is >set and 'restart when requests terminate abnormally' is set. > >Originally they were both checked. And in IIS Management I set >the Recovery >to "Restart the service" on bother First and Second failure. It failed. > >> 3) check your code. Do you have some pages with super long >running times. >Perhaps extra long queries? These tie up threads. >> Check the CF serverlog for warnings about long running >pages. "Log slow >pages taking longer than n seconds" should be set in the >> CFadman tool. > >The code has been the same for 10 months, core part I mean. We >used to have >IBM Netfinity until two months ago switched to the lighter, >smaller Dell >ones - you know how big and heavy those IBM ones are. Well, >never had any >such issue with IBM then. Use mostly stored procedures for any >heavy/frequent queries. session variables are set to 20 >minutes timeout. > >> 4) what is limit simultaneous requests set to? suggested is >3-5 per CPU >IIRC. >5 > >I've tried many different things but issues still exist, >pulling hair out... > >----- Original Message ----- >From: <[EMAIL PROTECTED]> >To: "CF-Talk" <[EMAIL PROTECTED]> >Sent: Thursday, February 06, 2003 2:01 PM >Subject: RE: why does CF Server times out so often? > > >> A ton of things to check for sure... >> 1) are you using ODBC connections to Access? This used to >be an issue of >the ODBC driver fouling the works up. We had to schedule the >CF srevice to >bounce everynight. All was fine after that. >> 2) in the CFAdmin tool, make sure 'restart after n >unreponsive requests' >is set and 'restart when requests terminate abnormally' is set. >> 3) check your code. Do you have some pages with super long >running times. >Perhaps extra long queries? These tie up threads. Check the >CF serverlog >for warnings about long running pages. "Log slow pages taking >longer than n >seconds" should be set in the CFAdmin tool. >> 4) what is limit simultaneous requests set to? suggested is >3-5 per CPU >IIRC. >> >> just somethings I'd be looking at first >> >> the log error of >> "Windows NT error number 232 occurred. " is common due to >users giving up >on the HTTP request and moving on. >> >> this error bothers me >> "Error attempting to write location redirection to web server >> (Windows NT error number -2147467259 occurred)" >> it could be related to the NT 232 error, but...perhaps you have a >CFLOCATION tag that is going into an infinite loop??!?!? >> >> As for "single threaded" setting, I'd read up on it. Check >out the docs >and articles at macromedia's CF site. >> >> Doug >> >> >-----Original Message----- >> >From: Ye Wang [mailto:[EMAIL PROTECTED]] >> >Sent: Thursday, February 06, 2003 1:24 PM >> >To: CF-Talk >> >Subject: why does CF Server times out so often? >> > >> > >> >Hi, >> > >> >Other people might already ask those questions on this list >> >before, but I couldn't find any old mail that answers my >> >questions exactly. So here they are, if anyone can throw some >> >light on it, really appreciate! >> > >> >Machine: Dell >> >CF: CF 5 >> >On our web server CF times out very frequently. Sometimes once >> >every other day, sometimes a couple of times a day. All sites >> >that running CF are down unless I restart the CF service or >> >reboot the machine. As you can imagine this has been quite >> >frustrating and annoying. One has to check the sites >> >constantly at all hours to make sure things are okay. It's not >> >session timeout or application timeout, it's simply cf server >> >down. I did try to let the windows/iis handle it, as set to >> >restart the service after it's terminated. But that failed as >> >well. Does anyone know why this happens? We never encountered >> >this problem before until two months ago we got this new >> >server from Dell. But I don't think it's the machine, at least >> >I hope not... >> > >> >Here are some repeated error logs I found in the cf log files. >> >Not sure if they are related to my problem above. >> >- application.log >> >", , Connection Failure. Status code unavailable." >> > >> >-server.log >> >"Windows NT error number 232 occurred. >> >Error number 232 occurred attempting to close connection to >> >web server. " >> > >> >- webserver.log >> >"Error attempting to write reply header back to web server >> >(Windows NT error number 10038 occurred) >> >Error attempting to write location redirection to web server >> >(Windows NT error number -2147467259 occurred)" >> > >> >Does anyone know what those mean, what's the cause and what I >> >can do to fix? I am not a system admin, so my guess is limited. >> > >> >One more question, there is this checkbox on CF Admin page >> >for "Single Threaded Sessions". Our old sys admin left it >> >unchecked. I wonder if it would affect server performance when >> >it's checked... >> > >> >lot Thx >> > >> >YW >> > >> > >> > >> > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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 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 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
