This ColdFusion 10 Update 8 (release date: February 27 2013) includes support for Google Maps JavaScript API v3, Mac OS X Mountain Lion 10.8.2 and JDK 1.7 Update 15. It includes all the bug fixes from previous updates of ColdFusion 10.

• ColdFusion 10 Update 8 was refreshed on February 28 2013 at 12 PM Eastern to fix an issue (Bug# 3508603) in the Google Maps JavaScript API. If you have installed this update before it was refreshed (your build number is 10.0.8.283965), then uninstall and reinstall the refreshed Update 8. If you are using the Google Maps JavaScript API or intend to use this feature, Adobe recommends that you apply the refreshed Update 8. The new build number of the refreshed Update 8 is 10.0.8.284032.

What's new

1. JDK 1.7: With ColdFusion 10 Update 8, ColdFusion 10 is now certified on JDK 1.7 Update 15.
2. Google Maps v3 Support
   
   1. With ColdFusion 10 Update 8, Google Maps JavaScript API library is upgraded from v2 to v3.
      
   2. For Google Maps JavaScript API v3, the API key used for Google Maps API v2 no longer works.
      
   3. ColdFusion map functions and ColdFusion map related tags are backwards compatible. If your ColdFusion application uses native Google Maps JavaScript APIs, ensure that the code base is updated to v3. For more information, see Google Maps JavaScript API v3 migration.
3. Mac OS X Platform Support: With ColdFusion 10 Update 8, support is now extended to 
   • Mac OS X Mountain Lion (up to 10.8.2)
   • Mac OS X 10.7.5 Server 

Prerequisites

1. If you have not already applied ColdFusion 10 Mandatory Update, apply it first. This step is not required if ColdFusion 10 build number is greater than 282462.
   
2. On a 64-bit computer, use 32-bit JRE for 32-bit ColdFusion and 64-bit JRE for 64-bit ColdFusion.
3. If the ColdFusion server is behind a proxy, specify the proxy settings for the server to get the update notification and download the updates. Specify proxy settings using the system properties, mentioned below, in the jvm.config for a stand-alone installation. Or, specify it in a corresponding script file for JEE installation. 
   • http.proxyHost
     
   • http.proxyPort
     
   • http.proxyUser
     
   • http.proxyPassword
4. For ColdFusion running on JEE application servers, stop all application server instances before installing the update.
   

Installation

For detailed instructions on how to install this update, see Server Update section.

Note:

• The ColdFusion 10 Windows installers available for download after March 5 2013 include Java 7 Update 15. Therefore, you can ignore the steps to configure an external JDK unless you want to upgrade the JDK to a higher update level. For more details on the new platform support for Windows 8 and Windows Server 2012, see this article.
  
• Microsoft Windows 7, Windows 8, Windows Server 2008, and Windows Server 2012 users must use the “Run as Administrator” option.
• The update can be installed from the Administrator of a ColdFusion instance or through the command-line option (For further details, see the link above).
  
• Windows users can launch the ColdFusion Administrator using Start > All Programs > Adobe > Coldfusion 10 > Administrator.

Mac OS X

1. If not installed, download and install JDK1.7. 
2. Configure JDK 1.7 with ColdFusion, for more details see this article.
3. Restart ColdFusion.
4. Install ColdFusion 10 Update 8.
   

Windows and other platforms

1. Install ColdFusion 10 Update 8.
2. Download and install JDK 1.7.
3. Configure JDK 1.7 with ColdFusion. For more details, see this article.
4. Restart ColdFusion.
   

• After applying the update, reconfigure the connectors. However, you can choose to ignore this step if you are on ColdFusion 10 Update 5 or later. In Mac OS X 10.8 and 10.7.5, it's necessary to reconfigure the connectors, irrespective of the update level. You can configure the using the wsconfig tool at {cf_install_home}/cfusion/runtime/bin. On Windows, you can launch this tool by choosing Start > All Programs > Adobe > ColdFusion 10 > Web Server Configuration Tool.

• You can encounter a Signature Verification Failed error when downloading and installing this update. To resolve this issue, download and install the ColdFusion 10 Mandatory Update first, before installing ColdFusion 10 Update 8. For more information, see this article. If this error persists, then download ColdFusion 10 Update 8 again. This error is primarily due to certain issues with download.
• If you get the following error when installing the update using the Download and Install option, ensure that the folder {cf_install_home}/cfusion/hf_updates has write permission: "An error occurred when performing a file operation write on file {cf_install_home}/cfusion/hf-updates/hotfix_008.properties"
  

Uninstallation

To uninstall the update, do one of the following:

• In ColdFusion Administrator, click Uninstall in Server Update > Updates > Installed Updates.
• Run the uninstaller for the update from the command prompt. For example, java -jar {cf_install_home}/{instance_home}/hf_updates/hf-10-00008/uninstall /uninstaller.jar

If you cannot perform the uninstallation with the steps mentioned above, it is possible that the uninstaller is corrupt. In such a case, you can manually uninstall the update by following the steps below: 

1. Delete the update jar from {cf_install_home}/{instance_name}/lib/updates.
2. Copy all folders from {cf_install_home}/{instance_name}/hf-updates/{hf-10-00008}/backup directory to {cf_install_home}/{instance_name}/
   

Remember

1. In the ColdFusion Administrator, if you see the update listed in both Available Updates and Installed Updates, it could be a caching issue. Do the following:
   1. Navigate to Server Update > Updates > Available Updates and check Check For Updates.
   2. Press Ctrl+F5 to remove the bulb notification from the top banner of the ColdFusion Administrator.
2. If ColdFusion server doesn't start automatically (ps -ef | grep -i coldfusion command indicates ColdFusion is running, but the ColdFusion Administrator cannot be accessed), restart the server manually after applying the update. This issue is rare and occurs on few Unix or Linux-based operating systems (when buffer allocation size of the machine console is almost zero).

Revisions:

March 6 2013: Added Update section for this article.