Hi again. I've posted a couple questions about trying to get ColdFusion 9 installed in distributed mode. I have it working in my client's staging environment but not in production. I've been messing around with their staging servers, trying to figure out what breaks it and what doesn't. I've run into a few oddities and I thought I'd post them here to see what people might know about what's going on in the background.
Let's say I have two 32-bit win2k3 servers: IIS: 192.168.1.10 CF: 192.168.1.20 On the IIS server I've set up the following directories and files: d:\ColdFusion9\runtime\lib\wsconfig\jrun_iis6.dll d:\ColdFusion9\runtime\lib\wsconfig\jrun_iis6.ini d:\ColdFusion9\runtime\lib\wsconfig\jrunwin32.dll d:\ColdFusion9\runtime\lib\wsconfig\wsconfig.properties d:\ColdFusion9\runtime\lib\wsconfig\1\jrun_iis6_wildcard.dll d:\ColdFusion9\runtime\lib\wsconfig\1\jrun_iis6_wildcard.ini d:\ColdFusion9\runtime\lib\wsconfig\1\jrunserver.store d:\ColdFusion9\runtime\lib\wsconfig\1\README.txt d:\ColdFusion9\runtime\lib\wsconfig\1\LogFiles\*.log I would have thought that jrunserver.store would need to contain "proxyservers=192.168.1.20:51011". However, whenever I put that in there and restart IIS, the next time I hit the site, it overwrites the file with "proxyservers=". I guess jrunserver.store isn't really used for anything, but instead ColdFusion uses the value in d:\ColdFusion9\runtime\lib\wsconfig\1\jrun_iis6_wildcard.ini under the bootstrap line. I should point out that I have CF9 configured to listen on port 51011. This was the default port for CF7 and for some reason when I installed CF9 it used the same port even though I read that CF9 is supposed to use a different port. I guess it must have picked out that setting from somewhere. The first time I run a page against IIS after a restart, I'll get the following log messages written in d:\ColdFusion9\runtime\lib\wsconfig\1\LogFiles: 2010-07-15 16:41:12 jrISAPI[init:5592] JRun 4.0 (Build 108795) JRun ISAPI Extension - Aug 29 2009 11:51:27 2010-07-15 16:41:12 jrISAPI[init:5592] JRun ISAPI Extension DLL Attaching 2010-07-15 16:41:27 jrISAPI[ 280:5592] could not initialize proxy for 192.168.1.20:51011 However, the connection is made fine and things work with no problems. Does anybody know why I'm getting this "could not initialize proxy" error message, even though things end up working fine? I'm just looking for any clues that might help me diagnose why this is not working in production even though it's working in staging. Thanks again, - Andrew. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology-Michael-Dinowitz/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:335400 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
