Entries Tagged as “Adobe ColdFusion”

Win $1000!! ColdFusion 11 Mobile Application Development Contest

October 20, 2014 / Elishia Dvorak

  Adobe ColdFusion | Adobe ColdFusion 11 | Announcements | CF Summit | ColdFusion | ColdFusion 11 | Mobile

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

Updates for ColdFusion 11, ColdFusion 10 and ColdFusion 9 released

October 14, 2014 / Krishna Reddy

  Security | Adobe ColdFusion | Adobe ColdFusion 10 | Adobe ColdFusion 11 | ColdFusion | ColdFusion 11

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

  Adobe ColdFusion | customers | Success Story

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]/workers.properties 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 workers.properties 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.

Deeper insights into ColdFusion logging mechanisms

September 16, 2014 / HariKrishna Kallae

  Administrator | Adobe ColdFusion | Adobe ColdFusion 10 | Adobe ColdFusion 11 | ColdFusion 11

In ColdFusion, you can use ColdFusion Administrator for changing your logging properties under Debugging & Logging > Logging Settings :

  1. Log location
  2. Maximum file size
  3. Maximum number of archives
  4. Requests taking longer time
  5. CORBA calls
  6. Logging for scheduled tasks
A detailed insight into each of this is available at http://hkallae.wordpress.com/2014/09/15/deeper-insights-into-coldfusion-logging-mechanisms/

How to change/upgrade JDK version of ColdFusion server

September 16, 2014 / Nimit Sharma

  Adobe ColdFusion | ColdFusion | General

This post is from my personal blog nimitsharma.wordpress.com


In this post, we discuss how to upgrade the latest minor version of JDK(Java Development Kit) of the ColdFusion server. ColdFusion can run only on top of JDK or JRE with Server VM. Oracle also started providing separate download link for JRE and Server JRE. ColdFusion only works with JDK or Server JRE and not with Client JRE [For more details refer article].

There are two ways to change the JDK or Server JRE of the ColdFusion server:
  1. Using ColdFusion administrator console.
  2. By changing the JDK or Server JRE path from the jvm.config file.
1. Using ColdFusion administrator console.
2. By changing the JDK or Server JRE path from the jvm.config file

Important Note:

  • It is not recommended to change the JDK version on the production servers without any prior testing in the staging environment.
  • Any SSL certificates added to the previous JDK will also need to be re-added to the new JDK(cacerts) file.

Blue Mango Theme Design By Mark Aplet

Super Powered by Mango Blog