> We used to do this before JRun4 and *MX, but now we are > upgrading and cannot seem to get the three to live together > happily. We have run the JRun4 web config tool, and my CF > peer has done the equivalent for CF. Now when I try to open > a jsp on port 80 (that works fine on port 8100) I get the > following (from the CF jvm). Of course, we have checked our > licensing and believe all is properly configured.
You can't have CF MX and JRun 4 working with a single IIS virtual server simultaneously. You have at least two options, though: - create separate virtual servers for each, then configure each with the appropriate version of wsconfig, or - replace the "standalone" version of CF MX with CF MX for JRun Note that CF MX and JRun 4 both use the JRun 4 connector to talk to IIS. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ voice: (202) 797-5496 fax: (202) 797-5444 ::::::::::::: dream :: design :: develop ::::::::::::: MXDC 02 :: Join us at this all day conference for designers & developers to learn tips, tricks, best practices and more for the entire Macromedia MX suite. September 28, 2002 :: http://www.mxdc02.com/ (Register today, seats are limited!) :::::::::::::::::::::::::::::::::::::::::::::::::::::: ______________________________________________________________________ Your ad could be here. Monies from ads go to support these lists and provide more resources for the community. http://www.fusionauthority.com/ads.cfm Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
