Skip to main content
Participating Frequently
August 6, 2010
Question

CF 9.0.1 / IIS 7: able to reach stopped CF instance

  • August 6, 2010
  • 2 replies
  • 2700 views

Hello,

I've been unable to find a solution to this problem so maybe someone here can point me in the right direction.  We're running CF 9.0.1 on Windows Server 2008 with IIS 7.  We have three identical production websites each with its own IIS and CF instance.  I've linked them using the wsconfig tool but we've noticed some odd behavior.  If I stop one of the CF instance services from the server administrative tools, I'm still able to hit the web site.  We suspect that maybe even though the wsconfig tool says that each instance is linked to a different site, perhaps all the sites are somehow sharing the same JRun server?  Has anyone experienced anything like this, or can anyone recommend something to try?  I greatly appreciate any insight.  Thanks!

    This topic has been closed for replies.

    2 replies

    Charlie Arehart
    Community Expert
    Community Expert
    August 6, 2010

    You could identify the instance with this code:

    (Someone might also propose running the CF Admin to see what it would report, but the default in multiserver mode is to access the Admin via the built-in web server, not IIS, so unless you take extra steps to enable that, you may not be able to access the Admin via IIS against each site separately. You could call the Admin API to get various information as it would be reported in the Admin, but the above is an "old school" pre-Admin API way of getting the info.)

    /charlie

    /Charlie (troubleshooter, carehart. org)
    wstoeckelAuthor
    Participating Frequently
    August 6, 2010

    I'm still able to access the admin and the admin for each site.  For some reason it always assigns the CF Administrator site a different # so that seems to be intact.

    Charlie Arehart
    Community Expert
    Community Expert
    August 6, 2010

    But are you accessing the Admin using the built-in web server? That would be very different and not related to IIS.

    And what do you mean "assigns it a different number"? Are you referring here to the port for the Admin, such as 8301, 8302, or the number within the IIS wildcard mapping you referred to previously? And if the latter, what you do mean "always assigns a different number"? I thought you were saying before that it reverts back to some one number despite your changing it. Do you now mean that it really changes somehow to a new number (on a CF restart)? That would be very odd.

    You also didn't answer if it's a restart of CF that you were referring to in the first note.

    Just trying to help. Please don't take any offense in my pressing these points.

    /charlie

    /Charlie (troubleshooter, carehart. org)
    wstoeckelAuthor
    Participating Frequently
    August 6, 2010

    Upon more investigation, each site's handler mapping is pointing to the same \lib\wsconfig\#\jrun_iis6_wildcard.dll and manually changing this number gets overwritten as soon as the service is restarted.  Is there somewhere I can hardcode this in?