We recently moved one of our CF projects to Amazon Web Servers and
have started to get the 500 internal server error. This happens
regularly when we run a stored proc with does a lot of DB processing.
It often takes more than 300 seconds. I've set all the CF timeouts to
300 secs so why don't I
In CFADMIN did you enable *Enable HTTP status codes under Server
Settings Settings?
That will show a 500 from ISS Rather then the ussua; CF error.
Paul.
*
On 27/01/2012 10:21 PM, Stephen M wrote:
We recently moved one of our CF projects to Amazon Web Servers and
have started to get the 500
Hi Steven,
you don't mention what OS you are running but in general with 64bit
machines it is good to double the old 32 bit recommendations as a first
pass in server tuning.
For 2008 R2 the OS takes a gig or more with its trick memory free space
caching and its a good starting point with CF
