Skip to main content
February 4, 2008
Question

HTTP 500 Error - inplace of Debug Info.

  • February 4, 2008
  • 2 replies
  • 592 views
I have CF8 Developer Edition installed on a Win XP Home platform.

Normal debug information displayed when a problem occurs is being replaced occasionaly by the standard MSIE 7.0 HTTP500 Error page - which contains no debug information. Any ideas whats causing MSIE to substitute the page for the normal (very useful) debug information?
    This topic has been closed for replies.

    2 replies

    Inspiring
    February 5, 2008
    > HTTP500 Error

    In a CF context, this means the CF (or, more likely, JRun) encountered a
    terminal error whilst processing the request. Basically the CF thread
    processing the request crashed. You don't get the debug, because CF
    stopped servicing the request.

    It'll - almost certainly - be down to an error in your code.

    These are often quite fun to track down; but look for endless loops in
    which large amounts of memory are allocated, or out-of-control recursions,
    and that sort of thing.

    --
    Adam
    February 5, 2008
    Yup - quite fun - those are the words I was looking for earlier :)

    I've resorted to putting cfexit's in the code to try and stop processing ahead of where the problematic code may exist. So far the problems are not limited to a single type of error - I've had one instance where the field declared in an insert statement didn't match the field in the db and a couple of others that dealt with string manipulations.

    Makes a lot of sense that the jrun engine is crashing and preventing the display of the error message.

    Is there a log file somewhere that may be capturing the error information just prior to the crash?

    quite fun indeed...

    Thanks for the help.

    TropSi
    February 5, 2008
    assuming you've enabled debugging with your ip address?