Hi all! I just want to make sure I'm not missing something here. We have our server (CF 5.0 on Solaris) set to timeout requests at 30 seconds and restart the server after 3 long-running requests. We've found this to be optimal if the server hangs due to one application losing a datasource (and we have several different apps and can't let one bring them all down). However, I just realized that it also counts requests exceeding the set time that have the URL parameter of RequestTimeout=XXX (above what the admin is set at).
This seems like a flaw because there are pages that will always run above the admin setting and I can't have the thing restarting every 3 of them. You would think it would overlook the ones specifically stating they will run longer. Otherwise the whole process stops and session variables are lost. Is there a workaround or something I'm missing? Thanks! Cathy ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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 Your ad could be here. Monies from ads go to support these lists and provide more resources for the community. http://www.fusionauthority.com/ads.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
