Reconfigure Apache Connector on Mac, Mountain Lion & CF10

ColdFusion 10 server updates
ColdFusion 10 server updates
ColdFusion 10 server updates informs to reconfigure connectors using wsconfig tool.

I’ve had to dabble through a few updates of ColdFusion 10 so far, and I’ve noticed that some of the updates require reconfiguring the Apache connector.  Something I hadn’t done before in CF9.  The main reason I had discovered this and needed it was the bug fixes in update # 1 that managed to fix problems with CGI variables.  I needed access to cgi.redirect_url and cgi.redirect_uri since I’m using Mod_rewrite rules for my urls.

For starters, you have to manually remove the Apache connector.  If you try to reconfigure right off the bat, you’ll be told that “This web server is already configured for ColdFusion.”

To get started, do yourself a favor and stop both Apache & ColdFusion 10.

For Apache, in a terminal window (I like iTerm), enter:

sudo apachectl stop

For ColdFusion 10, in a terminal window (if single server install) enter:

cd /Applications/ColdFusion10/cfusion/bin

./coldfusion stop

Here are the manual steps from the Adobe article on Installation Considerations:

  • If ColdFusion uninstaller is not able to remove the connector for Apache (for example, in the case of Mac OS X), do the following to manually remove it:
    1. Delete the mod_jk.conf found in
    2. Delete {cfroot}/config/wsconfig/1folder which has the Apache connector file,
    3. Remove the following line from {apache_install_location}/conf/httpd.conf file:
      Include “{apache_install_location}\conf\mod_jk.conf”.
    4. Delete the file {apache_install_location}\conf\mod_jk.conf

You can faithfully follow the above steps, but know that #4 is the same as #1.  Also, # 2 – I’ve noticed for myself that my /config/wsconfig/ directory contains two files, a wsconfig.log and files.  If I leave those files there and try to run the steps to reconfigure Apache, I’m still told “This server is already configured for ColdFusion.”  If you get this error, do yourself a favor and just delete the entire “wsconfig” directory and the included two files.  The Apache connector will recreate the folder & files.

To reconfigure Apache, in a terminal window type (again, if you are doing single server install – and chose default locations):

cd /Applications/ColdFusion10/cfusion/runtime/bin

sudo ./wsconfig -ws Apache -dir /etc/apache2 -v

You’ll be prompted for your account password.  Wsconfig needs additional privileges to create folders & files in protected directories.  If you try to execute without it you’ll get some strange “” type of errors for each file/folder it tries to create.  My command above is also assuming you’re using the default Apache located in /etc/apache2.  If you are using a different version of Apache, or installed Apache after the fact in a different location, then please update that part of the directory path.

Here is what you should likely see once the wsconfig is running:

command line: -ws Apache -dir /etc/apache2 -v
Could not find file /private/etc/bin/httpd
Using Apache binary /usr/sbin/httpd
Server version: Apache/2.2.22 (Unix)
Could not find file /private/etc/bin/apachectl
Using Apache control script /usr/sbin/apachectl
Parsing Apache configuration file /private/etc/apache2/httpd.conf
Exec'ing chmod 777 /Applications/ColdFusion10/config/wsconfig/1
Set permission to 777 on /Applications/ColdFusion10/config/wsconfig/1
Exec'ing chmod +x /Applications/ColdFusion10/config/wsconfig/1/
Set permission to execute on /Applications/ColdFusion10/config/wsconfig/1/
Created file /Applications/ColdFusion10/config/wsconfig/1/
Wrote file /private/etc/apache2/httpd.conf
Added ColdFusion configuration to Apache configuration file /private/etc/apache2/httpd.conf
Created file /Applications/ColdFusion10/config/wsconfig/1/README.txt
Wrote file /Applications/ColdFusion10/config/wsconfig/
Exec'ing /usr/sbin/apachectl restart
Restarted Apache server
The Apache connector was installed to /private/etc/apache2

Congrats, you’ve reconfigured the Apache connector on your Mac.  Apache got restarted with this process.  Don’t forget to restart ColdFusion:

cd /Applications/ColdFusion10/cfusion/bin

./coldfusion start

You’re done!

OSX Mountain Lion upgrade broke my Address Book (contacts)

After I upgraded to Mountain Lion I could no longer open up my Address Book (Contacts).  It was constantly crashing whenever I opened it.  I tried deleting preferences and reopening but had no luck.  It seemed really odd that it would be throwing bad_exec kernel type of errors.

I tried looking at a bunch of blog posts to try and troubleshoot this thing but none of the advice helped.  Most advice suggested things like removing the Address Book from the dock and re-adding but you can’t even do that with Mountain Lion – only Lion or Snow Leopard.  There was a seemingly helpful forum post on Apple.

I tried to think about all the things that integrate or use the address book and it put me on the right path.  I had an iCloud account and my settings for Mail & Address had my iCloud address book set to sync.  I tried un-checking that, and removing the existing contacts on the Mac (it’s in the cloud after all).  Still no luck though.  No matter what I did with the iCloud settings Address Book still wouldn’t open.

Ok, I also use Thunderbird and I know it reads the Address Book for contacts so I tried making sure Thunderbird was closed before launching but still no luck.

Then I struck some gold..  I realized that I had my Plaxo Assistant open in the toolbar.  After I quit it and made sure the process was closed in Activity Monitor I could open up my Address Book again and it worked normally.

So the Plaxo Assistant (toolbar helper) on Mac was the culprit and you can’t currently run it on Mountain Lion.  It causes crashing in Address Book.

I did some digging and found this blog post from Plaxo:

So they openly announce that they are not going to support Mountain Lion?  That seems like a really stupid thing to do.   Since I am currently a VIP Platinum Support user – I sent them an email.  This is part of the response I got back:

We understand that you are facing issues with the Plaxo sync service on your Mac Mountain LION system, but you showed us the interest in our product and you are also willing to continue the Plaxo service. Hence we have given you the additional information. Our engineers are constantly working on the Plaxo updates and are trying their best to stay compatible with all the offered devices. We have officially announced that we do not support the sync services with Mountain LION OS, however our engineers are always working on a fix to support this version too.

Ok, so what is it Plaxo?  Are you going to support Mountain Lion or not?  Get the feeling that engineering, marketing & support are not talking to each other?

In the meantime, I’ve uninstalled Plaxo Assistant and downloaded the iOS Plaxo app, it’s the only thing that does support iCloud.  Again, they make an iPhone app that supports iCloud but don’t have the foresight to refactor Plaxo Asistant to work with iCloud?

Anyway, hope this helps anyone else having problems with Address Book and also has iCloud & Plaxo.