See you around@NCDevCon!

Hope to see some of you at NCDevCon! I would be speaking on the charms of ‘CFBuilder & Mylyn’. The session is on 23rd May, 2:00-3:00pm. Looking forward to participating in a great conference and meeting many of our CFer friends!

CPU spike if TailView is kept open in CFBuilder

CPU usage of jrun service spikes if Tail View is kept open in CFB. The reason is that jrunsvc keeps log file opened and tail view gets the file handle every 100ms. This leads to CPU spike.
Tail View can be configured to get file handle after every 5seconds which reduces CPU spike considerably. You could do this at Windows->Preferences->HTML->Tailview->Change ‘Read Timeout’ to 5000

Opening a file in CFB from explorer

While attempting to open a file from outside CFB (.cfm/.cfc is set to open with CB), you may hit upon a ‘workspace in use’ error. This occurs in shared machines with different users. The workaround is to delete the .eclipse folder that gets created in the user’s home directory. After deleting, start CFB using -clean option. You should be able to open files from file system.

Encoding in CFB

ColdFusion Builder now treats all cfml content as UTF-8 encoded by default. This can be changed through preferences to suit the encoding of the file being edited.
Refer to Sandeep’s blog on ‘how to change encoding preference’.
Also, the forum post has similar issue answered.

What would you like to see in the next version of ColdFusion Builder?

The Storm (codename for next release of ColdFusion Builder) research survey is live and available at
Through this survey, we would like to know your feedback on the current version as well as what you think should be the driving features of the next version. Please spend some time to take the survey and help the CFB team move in the right direction while working on the next version.

Adobe Community Help updates

You can find some useful updates on Adobe Community Help Client (CHC) at:

Things to watch out while Installing CFB

1.Instructions to the pre-release and beta build users:
Before you install ColdFusion Builder release build,if you have applied the license key anytime that you have received from Adobe, please make sure to deactivate the license(Help->Adobe ColdFusiion Builder Deactivation…) with erase checkbox selected.Then uninstall the earlier builds.
If you are installing as plug-in please make sure to have fresh copy of eclipse rather than installing on top of the eclipse that was used for beta or pre-release builds.
If you are using CFB along with Flash Builder please make sure that you are using the released build of Flash Builder.

2.Eclipse Versions:
For plug-in mode installation of CF Builder you can use eclipse 3.4.2 or 3.5.1.It is recommended that you use 3.5.1.
Only 32 bit eclipse is supported.You can’t use ColdFusion Builder with 64-bit eclipse.
For Mac OSX, cocoa version of eclipse is not supported.Make sure that you use carbon version of eclipse.

3. Not able to see License screen?
If you are using either cocoa version or 64 bit version of eclipse, you may not see the license window of ColdFusion Builder.Also many features of CF Builder like color coding will be missing,Help->Adobe ColdFusion Builder Registration is disabled. So please make sure that you are using the right version of eclipse.

4.Why I don’t see color coding??
License window is a modal one and if you click on any file even before license window comes up, license window appears behind the eclipse/CFB and you may not observe this and you may see that color coding is missing.Please make sure to accept the trial license in the modal window and this issue won’t happen.

5.Can’t see ColdFusion perspective after installing ColdFusion Builder as a plug-in to eclipse

In case of ColdFusion Builder plug-in installation on Eclipse, when you uninstall ColdFusion Builder and reinstall plug-ins into a different directory than the initial install directory, then you may not see the ColdFusion Builder perspective.

  • Workaround incase of Eclipse 3.4.2:

    Install (i.e unzip) a fresh copy of eclipse and put the file by copying it from the eclipse_home\dropins to the newly installed new_eclipse_home\dropins.

  • Workaround incase of Eclipse 3.5.1:

    Remove the file named ‘’ from the eclipse_home\dropins directory by backing it up at some other location. Now launch the eclipse (This clear-off the eclipse cache).Now put back the file into the dropins directory and launch Eclipse to see the ColdFusion perspective.

  • If you don’t want to use the fresh copy of eclipse , reinstall ColdFusion Builder plug-ins into the same path as the initial installation plug-ins path.

Above issue can also come up if you are moving from Beta builds to final release build on the same eclipse as that is used for Beta installation.

To workaround this you can start using the fresh copy of eclipse or apply the same workaround as mentioned above.

6. ColdFusion Builder Licensing Error while launching:
Sometimes, you may come across the following error message while launching:

Can’t launch ColdFusion Builder with an error ‘Licensing for this product has stopped working’ with error code 150:30 or 148:3 with
detailed Error message: ‘This product has encountered a problem which requires that you restart your computer before it can be launched’

These errors might come when

1. Anchor service is not installed
2. FNPLicensingService is not running though it is installed
3. While installing ColdFusion Builder, there are other high memory consuming services running
4. Either System is running low on physical memory or virtual memory

How to work around this:

On Mac, please check whether you have Anchor Service installed or not in your system at path:Library/Application Support/Flexnet Publisher/Service/

For Win, you may check the path %Program Files%\Common Files\Macrovision shared\Flexnet Publisher\

If it is already installed, start FNPLicensing service (under services you can see the service with the name ‘FLEXnet Licensing Service’) manually and launch ColdFusion Builder.

If it is not installed or unable to start the ‘FLEXnet Licensing Service’ or above workaround is not working, uninstall and reinstall ColdFusion Builder as an admin user with the following guidelines.

  • While installing please make sure that you there are no other high memory consuming services running and have at least 4GB of usable hard disk space.

  • If it is on Windows, please make sure that ‘Windows Installer’ service is running.

The wait is over! Our baby bird has learnt to fly!

Finally… it’s Click->Buy ColdFusion Builder! And do I need to mention that we are super-excited? 🙂
Yes, the first ever version of ColdFusion Builder (CFB) has hit the online store! As most of you know, CFB is the first ever home grown IDE for ColdFusion(CF) development. It has always come up as the topmost feature/tool request from the community. CFB provides extensive IDE capabilities and makes CF development much more productive. I would like to congratulate all the stakeholders and to thank each and everyone who has helped make this product what it is today. I am sure it has been a very enriching journey for each one of us individually and as a team.
Just want to call out that we have made some major freeze, performance and startup time related fixes since the last available public beta version.
Here are some handy resource pointers:
ColdFusion Builder release notes:
Getting started with various tasks in ColdFusion Builder:
Getting started tutorials and videos:
ColdFusion Builder documentation:
We would also like to tell you that CFB can henceforth be updated via Help -> Adobe ColdFusion Builder Updates. This will look for any available updates and install the same. Any major fixes will be made available via updates, which means you would have them faster without having to wait for a major version release.

FTP in ColdFusion Builder

Wanted to write something for a while but wasn’t really getting enough time. And then Ben made my job easy. A lot of you were asking for FTP in ColdFusion Builder so here you go. Give it a shot!

Reporting one-off issues with CFBuilder

Would like to put a note here to all our beta users and request you to report to us any instability issues that you might hit upon while using CFBuilder. For example, such issues could be something like editor becoming unusable, IDE freezing up, editing becoming unusually slow, system slowing down due to use of CFBuilder, certain file/operation causing editor to behave abnormally etc. Since such cases or any other similar ones are either not very consistently reproducible, or they do not have any straightforward reproducible pattern, in order to report them to us you need to launch CFBuilder from console, take a thread dump, attach and upload it in forums or mail it to
Here is how you can do it:
On Windows – Start CFBuilder from console as CFBuilder.exe -consolelog -debug and keep using it. Once you hit upon the issue, take the thread dump using Ctrl+Break.
On Mac – Start CFB from Mac console. Go to /Applications/Adobe ColdFusion Builder/ Then run ./CFBuilder -debug -consolelog. Use the “ps” command to find out the process id (pid) of the Java VM. Invoke “kill -3 ” where is the process id of the Java VM.
A thread dump will be printed on the console where you started Eclipse. Since it may be long, in order to Copy & Paste it, it might be necessary to scroll and/or reduce the font size (xterm: right-click > font size > unreadable).
Alternatively, you can use the handy stacktrace tool at
All you need to do is to select the CFBuilder process id from the current list of processes and get the thread dump. The tool is free if you use Java Web Start to download it. And works on MAC, Linux & Windows.
Follow the link and select button “Launch” (press “OK” to “Run as a Java WebStart Application”)
Select menu Process > Select
In the combo box “Process ID” press the “…” button, select application and click OK
Pick menu Process > Thread Dump
File > Save As (enter some name e.g. C:\myThreadDump.txt)