Skip to main content
July 22, 2008
Question

Unresponsive Server at Startup

  • July 22, 2008
  • 1 reply
  • 510 views
When we restart one of our CF8 instances that instance always go into unresponsive status for 3-5 min before it will start to serve pages. Does anyone know what might be causing this issue or how to resolve it. We are using Windows 2008 (IIS7) and CF 8.0.1 in multiple instance mode connected to a NAS UNC share for content.
    This topic has been closed for replies.

    1 reply

    Inspiring
    July 22, 2008
    AGICroeder wrote:
    > When we restart one of our CF8 instances that instance always go into
    > unresponsive status for 3-5 min before it will start to serve pages. Does
    > anyone know what might be causing this issue or how to resolve it. We are using
    > Windows 2008 (IIS7) and CF 8.0.1 in multiple instance mode connected to a NAS
    > UNC share for content.
    >


    If you start the instance from a command line, you will get screens and
    screens of statuses of what is going on when. You could review that to
    see if there is anything you can tweak. But ColdFusion has never been a
    jack rabbit of a starter. And until it is completely started the
    unresponsive status is what is received.

    July 22, 2008
    Should I tell CF to refuse connections once it goes into the Unresponsive Status?
    stephend61837357
    Adobe Employee
    Adobe Employee
    July 23, 2008
    Try getting a thread dump after a reasonable amount of "startup time" has passed. Repeat every 10-15 seconds about 3-4 times.

    There is a technote on how to do this with CF started from the command line. You can also do this with a Windows service - "interact with desktop" has to be checked in the service.

    Technote 18339

    I wrote this some time ago for CF7 but it also applies with CF8 if you don't have the version with 'server monitor'.

    This will tell you what ColdFusion is doing and may give you some insight into where it's sticking. Email me the thread dump. It should be in the /cf8/runtime/logs/[servername]-out.log.

    I don't normally look at CF stuff anymore but we've had similar problems internally with our CF servers at times and these are often the hardest to track down.

    Stephen