Hello, apologies if this is not actually CF-related, but I haven't got the foggiest idea what to do next. We've been having a problem where a page was being executed twice, and thus duplicating everything.
I managed to track this down to the IIS logs, where I find that for some (but not all) CFM requests, a status 503 is being generated and sent back to the client. Then, a status 200 is being generated and send back. Both of these are accompanied by the requested CFM page being fully executed. After looking up about status 503, it is supposed to be a 'temporarily busy' type message, and I see that there is a Retry-After header which instructs the client to retry after the appropriate time. Monitoring CPU/RAM usage while requests are happening shows nothing unusual - the CPU is not constantly working or anything, and there's plenty of memory free. So, it appears that for the first request IIS is randomly deciding to send a status 503 with Retry-After header, and then executing the code regardless. Then the browser automatically sends the retry request and everything executes and a status 200 is returned. Does anyone have any idea why this is happening, or how it can be stopped? Thanks, Peter ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting, up-to-date ColdFusion information by your peers, delivered to your door four times a year. http://www.fusionauthority.com/quarterly Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:257870 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
