ugh, never worked? I beg to differ. I have not moved to CFMX yet, but this setting works. I have an app that is very DB intense and I have watched the logs pile up with "unreposnsive thread count has reached x" and when x = the "restart server on y unresponsive requests" the CF process did restart. In my experience this was DB related....long queries, Db down, etc. After working on the app we did the following: 1) worked on better SQL 2) raised the request time out limit per request and server wide 3) tweakd the "Restart Server on X Unresponsive Requests" setting in combo with the number of request limit.
Now we occasionaly get an entry in the CF logs with "unreposnsive thread count has reached x" where x is 0 or 1 and no server hangs. I don't mean to be crass, but you got to do some work on this stuff, it may not be CF's fault. Doug >> "Restart Server on X Unresponsive Requests" simply has never worked. > >I think the current behaviour is OK, as long as the "Restart >Server on X >Unresponsive Requests" works. I never have that many hung threads so I >can't confirm or deny. > >Jochem > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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 Get the mailserver that powers this list at http://www.coolfusion.com
