Today I decided to attempt an upgrade to Mountain Lion with my ColdFusion 9.0.1 install. I already successfully upgraded another machine running ColdFusion 10 but given the issues I had last year with Lion and ColdFusion 9 I was a little gun shy. But with just a few tweaks I learned from the CF10 install, the CF9 install went pretty smoothly.
First, before the upgrade I moved all my ColdFusion/Apache config to a separate config file included from the httpd.conf file: “Include /private/etc/apache2/other/*.conf”
/private/etc/apache2/other/coldfusion.conf
# JRun Settings
LoadModule jrun_module /Applications/ColdFusion9/runtime/lib/wsconfig/1/mod_jrun22.so
JRunConfig Verbose false
JRunConfig Apialloc false
JRunConfig Ignoresuffixmap false
JRunConfig Serverstore /Applications/ColdFusion9/runtime/lib/wsconfig/1/jrunserver.store
JRunConfig Bootstrap 127.0.0.1:51800
#JRunConfig Errorurl url
#JRunConfig ProxyRetryInterval 600
#JRunConfig ConnectTimeout 15
#JRunConfig RecvTimeout 300
#JRunConfig SendTimeout 15
AddHandler jrun-handler .jsp .jws .cfm .cfml .cfc .cfr .cfswf
Next, after the OS is upgraded to Mountain Lion I noticed an important line missing in the httpd.conf file. So I added the following line right above the first <Directory> tag:
NameVirtualHost *
Once I did that, all I had to do is restart apache and make sure ColdFusion was started. The apache restart command in Terminal is sudo apachectl restart. And that is all it took to make it work in my configuration.
The CFIDE directory had a 403 error, so to fix that I simply added the directory that was being aliased to my httpd.conf file.
<Directory "/Users/kbenore/cfdocuments/CFIDE">
Options Indexes FollowSymLinks MultiViews
AllowOverride All
Order allow,deny
Allow from all
</Directory>Again, restarted apache and everything works beautifully.
#1 by Larry C. Lyons on August 14, 2012 - 3:23 pm
When I upgraded to Mountain Lion my install also broke. In the http.conf file Include /private/etc/apache2/other/*.conf was commented out. Generally I don’t like including everything in that directory, so I ended up just including the conf files I wanted and or needed.
Also in Mountain Lion Apple removed the web sharing control in the Share panel. So you are forced to use the terminal. However Tyler Hall, the guy who wrote probably the best Virtual Host GUI for Apache on the Mac, VirtualHostX, released a control panel pane that adds Web Sharing back to the System Prefs. This is very useful if you’re as lazy as I am.
http://clickontyler.com/blog/2012/02/web-sharing-mountain-lion/
That said his VirtualHostX has saved me from tearing out my hair multiple times, highly recommended.
larry
#2 by James Aylesworth on August 17, 2012 - 10:10 am
This is great. Followed to the ‘t’ and all is now well. Thanks!
#3 by Kevin on August 21, 2012 - 9:46 am
@Larry – I found keeping everything I configure in the “other” directory helpful as Apache/Apple doesn’t overwrite that directory upon upgrades. I also have Apache running pretty much all the time. Occasionally I will restart it when I make a config change, but for me those times are so rare I can use the terminal for that. I do “cheat” a bit, for terminal commands I can’t remember I tend to write BASH scripts and then alias those. I have a BASH script in which I just type “apache restart” and presto I am done.
I remember playing with VirtualHostX. It is a good GUI tool for those more comfortable in that type of environment, but with all of the configurations I am managing I feel like I have more control modifying text files. Plus it forces me to utilize the geekier unix/linux/bsd-type tools.
#4 by Brek on September 16, 2012 - 4:58 pm
I’ve been having trouble setting up my local development environment on Snow Leopard and Lion.
There seems to be a problem with the version of mod_jrun22.so I’m using. The console tells me that what I have is the wrong architecture which I understand to mean I have either 32-bit or 64-bit and need the opposite.
I’ve tried various solutions I have found online, but I haven’t had luck. Do you have any insight regarding this issue?
#5 by Kevin on September 17, 2012 - 8:20 am
@Brek, no sorry I have not seen that particular error. You may need to do a fresh install of CF with the correct architecture for your OS. If your machine is newer, it is likely 64-bit. But if you are getting that same error with both the 32-bit or 64-bit CF packages, then it could be something else entirely (like an out of date Java virtual machine). Not really sure how to help with this one, since I have not seen that issue first hand.