ColdFusion10 - Important Web Server Connector Changes
Posted by Mike Brunt at 11:58 AM
9 comments - Categories: Web Servers | CloudComputing | Java-JVM | ColdFusion | JRun-J2EE
There is an important difference in the web server connector on Windows (wsconfig.exe) on ColdFusion 10 which of course moved ColdFusion as a Java Application Server from JRun to Tomcat as the Servelet Container. This applies to multiple instance installs.
On ColdFusion 9 and prior there was one wsconfig.exe utility only which lived in {drive}\JRun4\bin. In ColdFusion 10 the first main difference is the directory structure which changed very much for the better in my opinion, now every install has the same directory structure starting in {drive}\ColdFusion10. All instances you add will be under this root and the parent folder for each instance will be in the ColdFusion10 root and have the same name as the instance, so if you add an "instance_01" it will show up as {drive}\ColdFusion10\instance_01. Here is the main point relating to wsconfig.exe each instance you add has its own copy which you should use to connect ColdFusion10 to web sites it is located in...
{drive}\ColdFusion10\instance_01\runtime\bin.
If you use the one installed when you install ColdFusion10, located in Start > Programs you can get unpredictable results.
Adam Cameron wrote on 02/28/13 12:29 PM
Cheers for posting about this, Mike. I was caught out by this a few months ago when I was investigating clustering instances under CF10. I could not work out why I was seeing varying results when reconnecting the instances to Apache, not noticing sometimes I was using the default instance's connector, and sometimes one of the cluster node instances'. I was only expecting the one wsconfig.exe (as per JRun), and had not noticed I had a Windows Explorer instance opened for both CF instances, and was running wsconfig.exe from a randomly selected one each time I was running it. Talk about confusing (I am easily confused though ;-)--
Adam