Skip to main content
Known Participant
April 20, 2010
Question

ColdFusion 9 Fails after SQL 2008 Cluster Failover

  • April 20, 2010
  • 1 reply
  • 1979 views

All,

I have a ColdFusion 9 app server that seems to be failing when my SQL 2008 cluster fails over to the passive node. By failing, my IIS server does not respond to any .cfm requests about 4-5 minutes after the failover. It serves out static and .asp pages just fine. Restarting ColdFusion server service and rebooting the server itself does not fix the problem. The only fix is to fail the SQL cluster back to the original node.

Specs are as follows:

SQL - SQL 2008 SP1 64-bit active/passive cluster VM

CF - CF9 running on Windows 2008 SP2 64-bit VM

Erick

    This topic has been closed for replies.

    1 reply

    Inspiring
    April 20, 2010

    Can you show the settings summary for your datasource in the CF Administrator?

    On which layer does your cluster fail over? Does the passive node just take over the IP address of the active node or does it take over the MAC address as well?

    For faster failover you should always shorten the TcpTimedWaitDelay in your Windows registry.

    elarinAuthor
    Known Participant
    April 20, 2010

    I don't have access right now to get a screenshot of one of our datasources. I do know that we have the "Maintain connection" option enabled for all of our SQL datasources (we have more than one defined). I believe everything else may be the default setting.

    As for the failover, the passive node takes over the IP and MAC address.

    Erick

    Inspiring
    April 21, 2010

    I expect failover to improve if you reduce the TcpTimedWaitDelay, the default value of 4 minutes is suspiciously like the initial delay you are seeing. Then the next step would be to make sure you have a validation query defined on the datasource to make sure CF actually takes old connections out of the connection pool.

    You have check this is actually a CF problem and other tools on the same machine that Cf uis running can still connect to the datasource after a failover, right?