We have received few incidents wherein users were not able to start ColdFusion services after server reboot or while restarting the services manually.
Applications dynamically generate ColdFusion files and sometimes also deletes them, but ColdFusion does not remove any old files from the cfclasses folder.
If you have a huge number of websites on one ColdFusion server, it creates thousands of cfclasses depending on number of incoming requests.
Deleting all the class files of cfclasses folder and restarting the ColdFusion server.
If you are unable to delete the files, rename cfclasses folder and create an empty cfclasses in the same location.
To avoid such issues in future, you can manually delete class files at regular time intervals.
If you do not wish to save the class files, you can disable this feature in administrator from Server Settings > Caching
Save class files
When you select this option, the class files generated by ColdFusion are saved to disk for reuse after the server restarts. Adobe recommends this for production systems. During development, Adobe recommends that you do not select this option.
Adobe ColdFusion 11 | Announcements | ColdFusion | General | Updates
ColdFusion 11 Update 4 pre-release build has been refreshed to address an issue with the Elvis operator.
Follow the instructions available in the blog post mentioned below to install this update:
We look forward to your valuable feedback and suggestions.
NOTE: Users who have already applied ColdFusion 11 Update 4 pre-release build, they need to uninstall it and re-download the latest build of ColdFusion 11 Update 4. The build number after applying this update should be 11,0,04,293127(PreRelease).
Adobe ColdFusion Builder 3 | Thunder | Adobe ColdFusion Builder | CFBuilder | ColdFusion | General | Hotfix | Mobile | PDF Generation | Updates
Update 3 for ColdFusion Builder 3 is released.
This update is primarily a companion update to ColdFusion 11 Update 3 which ahs added support for PhoneGap 3.5.
This is just an Update for the ColdFusion Builder 3 installation that were installed prior to the build number 292483. Corresponding full installers with this update embedded were already released in December. Automatic update notification takes care of notifying you, if this update applies to your installation or not. So, if your installation is the one that was released in December, this update is not applicable and won't show you the notification.
This update has the following 3 bug fixes.
Remote servers details not retained on Builder restart.
Exception when generating build for mobile project
PhoneGap version for Mobile project should be updated to 3.5
Through ColdFusion Builder 3, you would get an automatic notification to apply the Update.
In the month of August 2014, we had refreshed the update 2 just fixing the bugs arised out of Update 2. Ram has blogged it as Update 3 mistakenly. It should have been blogged as Refreshed build for Update 2. Our apologies for the confusion with regard to the update number.
ColdFusion 11 Installers refreshed-Has fix for Server fails to start on enabling J2EE Session variables and Installation on Japanese OS
Administrator | Adobe ColdFusion | Adobe ColdFusion 11 | Announcements | Application Server | ColdFusion | Docs | General | Hotfix | Session Management | Updates
During first week of December 2014, we had released Full installers for ColdFusion 11 with update 3 in-built. The build number was 11,0,3,292480.
There were two issues with the build that was released(Full Installers only).
1) After Enabling J2EE Session Variables server hangs on restart/start.
2)On Japanese OSes, installer doesn't recognize the Japanese locale.
If you have applied the update 3 through Hotfix, these 2 issues won't arise for you. And also, #1 is not applicable for J2EE deployments done as EAR or WAR.
These two issues are fixed and we have refreshed the Full installers this week. The build number is: 11,0,3,292866
If you have come across #1, either you can download and use the new installer or apply the workaround on your existing server itself.
The workaround is:
Open the xml file C:\ColdFusion11\cfusion\runtime\conf\context.xml (Change it as per your installation path)
and uncomment the tag: <Manager pathname="" />
<Manager pathname="" />
Change it to:
<Manager pathname="" />
If you have come across #2, you have to download and install.