Skip to main content
October 20, 2011
Answered

CFIDE pointing to wrong server instance

  • October 20, 2011
  • 1 reply
  • 953 views

I am using CF 9 Enterprise and have multi instances (instance and server in CF 9 are used interchangably here - I find the term server to be ambiguous in this case) on the same machine.  They share a common CFIDE directory (mounted as a Virtual Directory under the website) and the CFIDE directories under c:\jrun4\servers\<servername>\cfusion.ear\cfusion.war have been renamed.

Problem is the CFIDE's of two of the instances (the last two that were created) are pointing to the same instance (the last one created).  I have looked everywhere for a config that controls this but cannot find anything.

So when I go to:

https://cfadmin1/CFIDE/administrator/index.cfm and https://cfadmin2/CFIDE/administrator/index.cfm both sites have Server: cfserver1

I need to know how to change the cfadmin2 console to point to Server: cfserver2

There are a few possible causes:

When the last instance was added, the c:\jrun4\servers\cfserver2\cfusion.ear\cfusion.wa\CFIDE directory not renamed.

This appears to have caused cfserver2 to use that CFIDE directory instead of the shared one.  Renaming the directory fixed this problem.

I noticed some issues with the wsconfig.properties file where cfadmin2 was improperly registered, but I:

1)  removed it from the cfserver2 instance

2)  restarted IIS and the CF services and

3)  readded the cfadmin2

to fix that problem.

Also looked at the neo-security.xml and neo-runtime.xml files of the two instances and did not find anything out of the ordinary

Now I am out of ideas...

    This topic has been closed for replies.
    Correct answer

    Got the answer now (from another source) - the cfadmin2 IIS site Handler Mapping for JWildCardHandler was pointing to the wrong dll.

    Cfadmin2 is IIS site #8

    In C:\JRun4\lib\wsconfig\wsconfig.properties, site 8 has a CF id of 6.

    6=IIS,8,false,""

    6.srv=localhost,"cfserver2"

    6.cfmx=true,<null>

    However, the JWildCardHandler info was pointing to the wsconfig directory for CF id 9 - which is a site in the cfserver1 instance.

    (IIS Manager, click on site, group by area, under IIS -> Handler Mappings, Edit JWildCardHandler)

    C:\JRun4\lib\wsconfig\9\jrun_iis6_wildcard.dll

    Changing this to corespond with the wsconfig.properties info fixed the problem.

    C:\JRun4\lib\wsconfig\6\jrun_iis6_wildcard.dll

    All works now.

    1 reply

    Correct answer
    October 20, 2011

    Got the answer now (from another source) - the cfadmin2 IIS site Handler Mapping for JWildCardHandler was pointing to the wrong dll.

    Cfadmin2 is IIS site #8

    In C:\JRun4\lib\wsconfig\wsconfig.properties, site 8 has a CF id of 6.

    6=IIS,8,false,""

    6.srv=localhost,"cfserver2"

    6.cfmx=true,<null>

    However, the JWildCardHandler info was pointing to the wsconfig directory for CF id 9 - which is a site in the cfserver1 instance.

    (IIS Manager, click on site, group by area, under IIS -> Handler Mappings, Edit JWildCardHandler)

    C:\JRun4\lib\wsconfig\9\jrun_iis6_wildcard.dll

    Changing this to corespond with the wsconfig.properties info fixed the problem.

    C:\JRun4\lib\wsconfig\6\jrun_iis6_wildcard.dll

    All works now.

    Charlie Arehart
    Community Expert
    Community Expert
    October 20, 2011

    Glad you got it sorted. I was just about to share code to help you confirm, in fact, if the requests were REALLY getting to the instance you thought they were.

    Here’s some code that should have been able to confirm:

    /charlie

    /Charlie (troubleshooter, carehart. org)
    October 20, 2011

    Thanks Charlie for the response.  Unfortuately the code did not make the page.  Could you post it for future use?  It should be useful.