Welcome to this new list of resources related to updating CF, the CF web server connector, Java, the PMT, FusionReactor, CFBuilder, and related features of interest to CFML developers.
(Last Updated: Jan 23, 2023)

See below for:

Links to updates available (and tips for applying them) for CF, Java, the PMT, FusionReactor, and related features

  • ColdFusion:

    While ColdFusion 10 and above offer an update feature within the CF Admin, Adobe does offer pages listing each of the updates for CF10, 11, 2016, and 2018 (and should offer one for CF2021, when its updates begin to be released).
    And while you may hit errors trying this, see the section below on Resources to help in applying such updates. As always, I can help with applying any of these updates.

    Note also that Adobe offers an "update release notes" page which highlights the key changes among all the updates for CF2021, CF2018, and CF2016. (We can expect such a page to be created when CF2021 begins to have updates.)

  • ColdFusion web server connector (wsconfig):

    After updating CF, note that most CF updates also off an updated web server connector, and it's often critical to apply that connector update, if the CF update we are implementing (or any we are skipping) updated the connector.

    Critical: As of the March 2020 updates to CF2018 and CF2016, it's IMPERATIVE that the connector be updated (if you apply those updates or skip from older ones to newer ones). I have a blog post explaining this.

    In CF2016 and above, the CF update technotes end with a table indicating which previous updates did require a connector update. In CF10 and 11, it's incumbent on YOU to review the technote of the update you are applying AND ANY YOU ARE SKIPPING to identify if there is a need to update the web server connector. Sadly, there is currently no single page indicating all the CF updates which do require such an update. I may add that here at some point.

    Finally, as for upgrading the connector, some great news for those on CF2016 and above is that Adobe has simplified the process, offering an "upgrade" button in the wsconfig UI, which will indeed upgrade the connector for any site selected. This puts the latest connector file--.dll file for IIS, or .so file for Apache--into place and offers to restart the web server.

    For those still on CF10 and 11, the process instead requires REMOVING and then re-ADDING the connector. Back in 2013 I offered a blog post with substantial detail on the process: CF911: Why/when you MUST update the web server connector for ColdFusion 10/11 and may have missed it, as well as Still more reasons to make sure you have updated your ColdFusion 10 web server connector.

    I will warn that many have ignored this need to keep their connector up to date, to their peril--in terms of bugs, poor performance, hanging connector connections, and more.

    Again, I can help with this.

  • Java:

    After taking care of updating CF and updating the CF web server connector as discussed above, the next most important thing for most folks is updating the JVM that CF uses. Since it's updated about quarterly by Oracle, and often has security fixes, it's important to keep updated. And updating CF to use a newer Java version can be a fairly easy process, taking just a few minutes (and a CF restart), if you are comfortable with the process.
    1. First, as for what version of Java you can/should be using for your CF version, that depends both on the CF version and your CF update level. This has been covered in various blog posts from Adobe, myself, and others over the years. My most recent one (Jan 2021) covers CF and Java versions over the past 10 years, and offers a a helpful table I created of CF vs Java versions that Adobe supports.
    2. As for getting java updates, note that Adobe now offers the latest Java updates (that it supports for supported CF versions in a new section at the bottom of its CF-related downloads page. FWIW, Oracle also offers the latest updates for Java here (including Java 8, 11 and above), for those who have an Oracle account. Archives of older versions here, including updates for Java 8, Java 7, and and earlier.
    3. As for the process of updating the Java that CF uses, that too has been covered by many over the years (sometimes in scant detail, leading to trouble, or not updated in many years). Perhaps the simplest thing for many is to watch a brief video created by Pete Freitag. I did a more extended presentation on the topic in 2021, Updating the Java underlying ColdFusion which was recorded and also offered on youtube.

      As I cover in that talk, there are indeed several points to be careful about (easy mistakes to make) when updating the JVM that CF uses. I will say first that I had covered some basic information about updating Java in past blog posts such as one for when a new Java version came out in 2019. Readers could get value from that. Same with subsequent posts, for other Java updates, where I may reiterate or update points, such as in Oct 2020, Apr 2021, and so on.

      As important, if you may attempt the JVM update on your own, I address several key problems one could encounter, and how to fix them, in this 2014 post which is just as useful now, CF911: 'Help! I've updated the JVM which ColdFusion uses, and now it won't start!'.

    Note that if you may be using Commandbox, it's very easy to update the Java underlying that (and even allow it to keep your Java automatically updated). See the docs page on that.

    But again, if you're just interested to "get it done", I can help with this.

  • FusionReactor:

    Recent versions of FusionReactor offer an update mechanism within the UI to tell you when an update it needed. Unfortuantely, older versions did not. I will note that I did a blog post in 2018 that would benefit most but especially those on such older versions (that don't offer the update within the UI). See my blog post. Updates can be found at the FR downloads page. The FR installer can be run in-place over a previous FR version.

    And you can find a list of feature changes for each update within a given version on the release notes page for each version. For instance, the release notes for FR 8, the release notes for FR 7, and the release notes for FR 6.

    Again, I can help with this.

  • ColdFusion PMT:

    The ColdFusion Performance Monitoring Toolset (PMT), added in CF2018, also has updates occasionally. In CF2018, one had to apply the updates manually. I have a blog post with more on that.

    In CF2021, a new "update" section has been added to the PMT UI, working just like the update mechanism in the CF Admin (since CF10).

    Again, I can help with this.

  • ColdFusion Builder:

    ColdFusion Builder can be updated from within Builder itself. Unlike CF, there is no single page listing all ColdFusion Builder 2016 updates. Here are the most recent updates (as of late 2020):
    Again, I can help with this.

  • Lucee:

    Lucee updates are applied from within the Lucee Admin and can also be found on the Lucee downloads page.

    If you have any problems applying Lucee updates, the Lucee community and team are available to help.

Upgrading vs updating

I should clarify that I am discussing on this page "updating" CF (and other things), by which I refer to updating within a given version, as opposed to "upgrading" from one version to another. The effort to upgrade/migrate CF from one version to another (like, for example, CF11 to CF2021, or even simply CF2018 to CF2021) is a very different effort and exercise than what I am discussing on this page.

When it comes to upgrading CF versions (migrating from one version to another), there are of course typically many new and changed features, and a greater chance of breaking changes--though Adobe does strive to maintain backward compatibily more than many vendors (for better or worse, in the eyes of some).

As for assistance in performing such an upgrade or migration, Adobe does provide release notes with each new release, and the docs often have pages helping with new features, changed features, and even deprecated features. There is also the "code compatibilty analyzer" available in the CF Admin, where a newer CF release can be told to look at code and assess it for compabiity issues between a given CF version and that newer one. I can also assist with migration challenges on a consulting basis, as can others or the wider CF community.

When it comes to upgrading Java versions, a factor of first importance for Adobe CF users is to make sure that the newer Java version you want to move to is one that Adobe supports. again I have a table discussing that.

And whether one is using CF or Lucee, something to beware when upgrading Java versions (such as Java 8 to 11, or 11 to 17) is that both engines have features that compile CF and other code on the fly and save it for later reuse, using the Java version in place at the time of that compilation. If you change to a newer version, you need to delete such compiled java classes (while CF or Lucee is stopped). In CF, this is referring to folders under your CF instance (cfusion or others), including "stubs" and then the wwwroot/WEB-INF and folders under it including cfclasses (not "classes)", cfc-skeltons, and rest-skeletons. If you'd rather not delete them, you could also move or rename the folders. CF will create them anew if no there on startup. Finally there may be need to perform other steps (related to CF) when upgrading Java from one major version to another--especially on Windows, where some ms*.dll files may need to be moved from the new Java version's folders into CF's own folders. I discuss this in my resource, CF911: 'Help! I've updated the JVM which ColdFusion uses, and now it won't start!'. In fact, I have a number of resources related to doing updates, and I list those next.

Resources to help in applying updates to CF, the JVM, the web server connector, and more

Again, you may hit problems on doing the update above. I have written various blog posts to help.

Getting help in applying such updates, from Charlie Arehart

If you have not applied these various updates, this is something I can help with.

First, while the updates CAN go easily enough for anyone to do, it can also just as likely fail which leaves most people dead in the water. And while I offer above many resources to help, I can directly help resolve such update problems quickly, via my remote online consulting. I can make sure any such update is done well and quickly, generally in 15-30 minutes for each update (which includes making sure there are no failures in applying the update, as well as offering any guidance in considering and applying the update.)

As an alternative, I am now offering a new annual subscription service to implement such CF, JVM, and FusionReactor updates on your server, as they are released.
  • We could either work together remotely (via shared desktop), or you could allow me to remote in directly (via remote desktop, or another online means you may prefer)
  • We would choose a service-level agreement for how quickly you would want updates implemented after their release (some folks prefer to wait days or weeks after a new update, while others want them implemented as soon as possible)
  • I would confirm after each update that the CF Admin is working as well as a single page of your application that you would provide for me to test. Note that you would be responsible for testing your application beyond that, after the CF restart. If there are any problems, I can of course help solve them--as billable time under my normal consulting. But if you may opt to have me revert the update, I will do that as part of this service, including later applying that update again when you are ready
The base cost is US$400 per year, with the following clarifications:
  • This base rate covers a single CF instance and includes all updates to the given version of CF that it's running, as well as its CF web server connector (when a CF update calls for it to be updated), and any update to the given version of the JVM that that single CF instance runs on
  • Any other instances on the same machine are an additional $200/yr per instance
  • If you have FusionReactor, updates to that can be done as a separate charge: $100/yr for all FR updates on a single instance, with additional instances on the same machine being an additional $50/year per instance.
  • Finally, these rates presume I would be allowed to perform the update between the hours of 7am to 10pm US Central time, Mon-Sun If you require I do the work overnight/outside those hours, the annual rates above would be doubled.
Considering that there are typically a few updates each year to each of CF, the web connector, the JVM CF runs on, and FusionReactor (totaling over a dozen between the four of them), this subscription price represents a considerable discount off my normal hourly consulting rate.

More important for you, by committing to have me implement the updates for you, it ensures that they get done, correctly and quickly. Each update should take about 15 minutes, including the restart of CF which each requires and confirmation that the CF admin is accessible/functioning after the restart. (We would coordinate when to do that restart and initial testing.)

For more information, reach out to me via the contact information on the CArehart Consulting page.

Managed Hosting Services provided by
Databank Dedicated Hosting