Win $1000!! ColdFusion 11 Mobile Application Development Contest

October 20, 2014 / Elishia Dvorak

ColdFusion 11 provides a single platform to develop, test, and debug mobile applications in one end-to-end workflow leveraging your existing CFML skills.  

The Adobe ColdFusion Team is sponsoring a mobile application contest where the winner will receive a $1000.00 gift card prize.  More details below.  




Good luck!! 


And please help us spread the word!

Read More

Resolving "500 Internal Server Error" with ColdFusion 10 Update 14

October 16, 2014 / Krishna Reddy

We have seen that some of you have not been able to get the web server connector working after applying update 14.

We did our investigation and following is our finding.

The connector binaries of ColdFusion 10 update 14 are built on top of  VC++ runtime 2012 update 4.

Installation of VC++ runtime requires admin privileges. If the ColdFusion service runs as administrator or system account, the update itself install the VC++ runtime as this account would have installation privileges.

If your ColdFusion service account is not running as administrator or system account, applying the hotfix from administrator can't install VC++ runtime and you will get "500 internal server error" after configuring the connector.

In this case, you need to manually install VC++ runtime 2012 32-bit and/or 64 bit depending on whether Web server is 32-bit or 64-bit.

You can download VC++ runtime here at:

When you install hotfix manually, administrator privileges are enforced and so the installation of VC++ runtime is automatically taken care by the updater.





ColdFusion 10 support with Java 8

October 16, 2014 / Krishna Reddy

With Update 14 for ColdFusion 10, Java 8 is supported.

If you are using ColdFusion Web services you will have to do a one-time change manually.

You should copy tools.jar manually from {JDK8_Home}/lib to {cf_install_home}/cfusion/lib/. ColdFusion Web Services will fail if this is not done. Only JDK contains tools.jar not the jre. You don't have to install JDK on the machine where ColdFusion is installed. You can just have jre 8 on this machine and get tools.jar from any other machine's JDK installation.

And also make sure that the earlier stubs are cleared fom {cf_install_home}/cfusion/stubs/ to get the newly compiled classes.

Originally ColdFusion 10 was shipped with jre 1.6. With that build we released tools.jar of jdk1.6.

For Windows there was a refreshed installer release. With this jre include was 1.7 and so we have shipped tools.jar of jdk1.7.

Since, we are not releasing new installers and still if you want ColdFusion to run on jre 1.8.

Unless you want Web services, it is not necessary that you have to upadte it.

The reason why we have not shipped this through updater is that it can break the existing users those who have n't upgraded their jre.

Updates for ColdFusion 11, ColdFusion 10 and ColdFusion 9 released

October 14, 2014 / Krishna Reddy

The following ColdFusion updates are now available for download:

ColdFusion 11 Update 2

This update contains fixes for vulnerabilites mentioned in the security bulletin APSB14-23.

For the details refer this technote.

ColdFusion 10 Update 14

This update includes Tomcat upgrade to 7.0.54, Tomcat connector upgrade to 1.2.40, support for JDK 8 and Apache 2.4.x, fixes for vulnerabilites mentioned in the security bulletin APSB14-23 and fixes for 63 other bugs.

For the details refer this technote.

ColdFusion 9.0.2, ColdFusion 9.0.1 and ColdFusion 9.0 security update

This update contains fixes for vulnerabilities mentioned in the security bulletin APSB14-23.

For the details refer this technote.


How we solved a connector issue after ColdFusion 11 Update 1

October 09, 2014 / Anit Kumar Panda

ColdFusion 11 update 1 was out and blogged about here. It included the fixes listed in the technote, out of which two (Bug# 3777189 & Bug# 3758172) were related to IIS. We would like to share one of our Customer experience and how we solved a connector issue after applying Update 1 in ColdFusion 11.

The Challenge

Recently we were contacted by a customer from a larger organization, who wanted the IIS fixes. They weren’t aware about the release of Update 1. Once we told them, they tried to apply the Update 1, but had issues with it. We suggested them the alternatives that can be used when there is a problem with direct application of the hotfix. The update was installed successfully and was confirmed from ‘Settings Summary’ page in the CF Administrator. The next step was to reconfigure the connector. The moment connector was re-configured, all the sites went down. There were approximately 15-20 sites configured with ColdFusion and the entire production went down. We checked the update logs and they were clean. The error reported was "Error 403 Access Forbidden" across all the sites.

The Solution

We tested the non CFM sites, and they were functional. Only the ColdFusion based sites were giving the forbidden errors. Thus we inferred that, the issue is either with ColdFusion or the connector configuration. We enabled the internet port for ColdFusion and there we go, it worked. This meant, ColdFusion was also working perfectly, but somewhere the connector broke. Even after trying all the ColdFusion based troubleshooting steps, basic windows troubleshooting, permissions check, ColdFusion logs etc., we were unable to fix the issue.

Then we decided to compare the settings with one of the development servers they had. And bingo, we found the root cause of the 403 error. “worker.cfusion.secret=yourSecret” was added by them in their {cf.home}/config/wsconfig/[magic number]/ as a part of connector shared secret setting. This is a part of ColdFusion 11 Lockdown Guide procedure. When the connector was re-configured, the previous settings with configuration information were erased. But the corresponding entry in the {cf.instance.home}/runtime/conf/server.xml was still looking for the related entry in and thus was throwing error.

The Result

Once the setting was updated, all the sites were up and running in seconds. The customer was very happy, as their sites were back on production. If the connector needs to be reconfigured, we have to first remove it and then re-configure it. Connector removal means, the changes made by the user will be lost. When the user re-configures the connector thereafter, we don't have any means to identify what configuration settings they previously had.

The Recommendation

Before you re-configure the connector, we strongly recommend the following:

Ø  Back up all connector configuration files. Connector configuration files are available at {cf.home}/config/wsconfig/


Note: The same has also been mentioned in the ColdFusion 11 Lockdown Guide as well.

Blue Mango Theme Design By Mark Aplet

Super Powered by Mango Blog