Which JDK is supported with ColdFusion 9, 10, and 11?

Adobe ColdFusion sometimes supports newer versions the
Oracle Java Virtual Machine (JVM) through ColdFusion updates and hot fix releases. This post lists the JVM version supported by recent ColdFusion releases, depending on CF updates applied. (The term JDK is also used, referring to the Java SE Development Kit, the most common form of JVM deployment used with ColdFusion.)

To be clear,
Adobe will support the latest point release within a supported major JVM release, as listed below for each version of ColdFusion.For instance, if JDK 7 is supported, it can be 1.7.0_01 (Java SE Development Kit 7u1) or 1.7.0_72 (Java SE Development Kit 7u72), which was the latest JDK 7 release available at the time of this blog post in November 2014.

By the same token, while this post lists the latest JVM/JDK supported for a given CF release, we continue to support as well the earlier JDKs listed for each CF release. For example, CF 11 with update 3 or later supports either JDK 7 or 8.

ColdFusion 11

Update 3 and later: JDK 8

Update 2 and earlier: JDK 7

ColdFusion 10

Update 14 and later: JDK 8

Updates 8-13: JDK 7

Update 7 and earlier: JDK 6

ColdFusion 9.0.2

CF 9.0.2 Cumulative Hot Fix 1: JDK 7**

If no CF hot fixes applied: JDK 6

ColdFusion 9.0.1

Cumulative Hot Fix 4: JDK 7 **

Cumulative Hot Fix 3 and earlier: JDK 6

ColdFusion 9.0

Cumulative Hot Fix 3 and later: JDK 7**

Cumulative Hot Fix 2 and earlier: JDK 6

**JDK 1.7 is only supported on
Mac OS X 10.7.3 and later. See this article for more
details. ColdFusion 9.0.X does not support Mac OS X 10.7. Therefore, Cumulative
hot fix 1 does not certify ColdFusion 9.0.X with JDK 1.7 on Mac OS X.

27 Responses

  1. Just asking for clarification. The statement regarding support of Java 7 for ColdFusion 9.0.x does not match original response from Rakshith when the CHFs for ColdFusion 9.0.x for Java 7 support were released.


    Also there were a lot of comments from those that tried and never could get ColdFusion to start with anything but the Apple Java 6 that was already installed on 10.7 and 10.8.

  2. In addition to the clarification Dave Epler has requested, does this mean – for instance – that CF10u14+ is /only/ supported on JDK8? Or should we be reading this in a more cumulative manner to indicate that CF10u7 and earlier were only supported on JDK6, CF10u8 – CF10u13 were supported on JDK6 and JDK7, and CF10U14+ are supported on JDK6, JDK7, and JDK8?

  3. Re this:
    “ColdFusion 10 Update 14 and later: JDK 8”

    So up-to-date versions of CF10 are *only* supported on Java 8?

    I know Java 7 is EOL come April 2015, but it’s still a supported Java platform *now*. So CF should run on it, shouldn’t it?

    What happened between U13 & 14 to make it no longer supported?


  4. @Ron and Adam, it is indeed that these are listing the latest versions of the JVM supported in each listed release. The point was to say “if you want to use a given updated JVM, you can but only with the CF releases listed”. Still, it’s a reasonable source of confusion so hopefully Elishia or someone at Adobe will update the lines to make it more clear.

    @Elishia, that said, thanks so much for offering this. It’s great to see the clarification for those who may have wondered what release supported what more updated JVM versions.

  5. @Adam Cameron: I think this may be wrong information. In the hotfix list they have fixed a bug to support JDK 1.7.51 or higher. So I think they support 1.7 with CF10 Updater 14.

  6. Hi, I upgraded to Update 3, and installed JDK 8_U25, and no luck- the CF Application service gets stuck on startup.
    Any idea if this only works with an earlier version of JDK 8?

  7. Hello, yes thank you Charlie- my problem is solved. It had to do with a JVM parameter that was no longer valid in JDK8- I simply had to remove it from the CF Admin JVM setup, and it started.
    Running on JDK 8 now. Thank you again.

  8. @Charlie, yes, I can! I had to remove the following from the JVM Arguments:

    I don’t recall why I had placed this initially- it was years ago, and must have done some optimization study, and added this. This causes CF 8 not to start! So had to remove it from the jvm.config manually.

  9. I have a current install of CF 10, Update 15 running on jdk1.8.0_25 with no issues. However, when trying to upgrade to
    CF 11, I having issues after running the migration wizard. These are the only entries in the Coldfusion-error.log:

    Jan 20, 2015 9:29:57 AM org.apache.coyote.AbstractProtocol init
    INFO: Initializing ProtocolHandler [“ajp-bio-8014”]
    Jan 20, 2015 9:29:57 AM org.apache.catalina.core.StandardService startInternal
    INFO: Starting service Catalina
    Jan 20, 2015 9:29:57 AM org.apache.catalina.core.StandardEngine startInternal
    INFO: Starting Servlet Engine: Apache Tomcat/7.0.54
    Jan 20, 2015 9:30:01 AM org.apache.catalina.util.SessionIdGenerator createSecureRandom
    INFO: Creation of SecureRandom instance for session ID generation using [SHA1PRNG] took [109] milliseconds.

    Here are the list of steps I performed:

    1. Current Environment: CF 10, update 15. on Windows 2008 R2 (64 bit)
    Running JDK 1.8_25 (64 bit) on D:Javajdk1.8.0_25jre

    2. Ran ColdFusion 11 Installer (ColdFusion_11_WWEJ_win64.exe – Update 3 included)

    (DID NOT run the migration tool after install):

    Installation Type:
    Server configuration

    Enterprise edition (64 bit)
    Serial Number: 1185-xxxx-xxxx-xxxx-xxxx-xxxx

    Installation Directories:
    Product: d:ColdFusion11

    Server Information:
    Web Server: Internet Information Server (IIS) (All)
    ODBC Services: not installed
    ColdFusion Server Profile: Development Profile
    ColdFusion Solr Search Services: installed
    ColdFusion .NET Integration Services: installed
    Microsoft .NET version: v4.0.30319
    .NET Java Port: 6091
    .NET Client Port: 6092
    RDS: disabled

    Disk Space Information (for Installation Target):
    Required: 1,872 MB
    Available: 10,238 MB

    2. Edited the JVM path in D:Coldfusion11binjvm.config to my existing (working) version under CF 10:

    3. Changed the D:ColdFusion11cfusionjettyjetty.lax file to reflect the same JVM (d:Javajdk1.8.0_25jre)

    4. Restarted CF 11 Services – all restarted successfully.

    5. Copied D:Javajdk1.8.0_25libtools.jar to D:ColdFusion11cfusionlib

    6. Restarted CF 11 Services – all restarted successfully.

    7. Ran Web SErver Configuration Tool (D:ColdFusion10cfusionruntimebinwsconfig.exe) to remove association with CF10

    8. Ran Web Server Configuration Tool (D:ColdFusion11cfusionruntimebinwsconfig.exe) to create association with CF11

    9. Went to http://servername/CFIDE/administrator/index.cfm and Migration Wizard starts.

    10. Ran through migration wizard with no errors – CF Administrator comes up.

    System Information
    Server Details
    Server Product ColdFusion
    Version 11,0,03,292480
    Tomcat Version
    Edition Enterprise
    Operating System Windows Server 2008 R2
    OS Version 6.1
    Adobe Driver Version 5.1.3 (Build 000094)
    JVM Details
    Java Version 1.8.0_25
    Java Vendor Oracle Corporation
    Java Vendor URL http://java.oracle.com/
    Java Home d:Javajdk1.8.0_25jre
    Java File Encoding Cp1252
    Java Default Locale en_US
    File Separator
    Path Separator ;
    Line Separator Chr(13)
    User Name {SERVERNAME}$
    User Home C:Windowssystem32configsystemprofile
    User Dir d:ColdFusion11cfusionbin
    Java VM Specification Version 1.8
    Java VM Specification Vendor Oracle Corporation
    Java VM Specification Name Java Virtual Machine Specification
    Java VM Version 25.25-b02
    Java VM Vendor Oracle Corporation
    Java VM Name Java HotSpot(TM) 64-Bit Server VM
    Java Specification Version 1.8
    Java Specification Vendor Oracle Corporation
    Java Specification Name Java Platform API Specification
    Java Class Version 52.0

    11 Stopped all CF 10 Services.

    11. Restarted CF 11 Services – Would not start. Error 1053.

    Any ideas?

  10. Here is a head scratcher:
    (Windows 64 bit)

    I use CF11 U3 as my base install. Thus it came with Java 1.8.0_25-b18.
    The footprint (ACTUAL byte size) of some key files after a FRESH CF11-U3 install:

    In the {cf-root}jrebin
    java.exe: 190,888 (showing as version 1.8.0_25_b18 in properties).
    java.dll: 157,096 (showing as version 1.8.0_25_b18 in properties)

    In the {cf-root}cfusionlib
    tools.jar: 18,182,147

    Then today I get Pete’s reminder (via hackmycf) that “When upgrading CF10 or CF11 servers to Java 8 you will need to copy the tools.jar file from the Java 8 JDK into your {cf-root}/cfusion/lib directory. Without this step your SOAP web service calls may fail”.

    Call me nervous, obsessive and anal, but I wondered if my CF11 U3’s tools.jar was ALREADY fixed (you would assume it would be, since CF11-U3 was already bundled with 1.8). So I installed fresh JDK 1.8.0_25_b18 onto a test instance (a clone of my live instance). It was obtained directly from the Oracle website.

    Not only is the tools.jar footprint different, but so are the other two key files that I spot checked, as follows:
    The footprint (ACTUAL byte size) from the JDK 1.8.0_25_b18 fresh install are:

    java.exe 190,856 (showing as version 1.8.0_25_b18 in properties).
    java.dll: 157,064 (showing as version 1.8.0_25_b18 in properties)
    tools.jar: 18,140,236

    The versions match up in both the CF11U3 fresh install and the test install from JDK from Oracle. So, WHY the footprint differences? And since we are told to use the Oracle tools.jar for 1.8 upgrades, yet it’s footprint differs from the one Adobe gives us in CF11U3, I am left scratching my head.

    Any opinions on this disconcerting observation?


  11. Now I know upfront that Java 1.8 isn’t supported on ColdFusion 9.0.2, but, I have a question none the less.

    If I patch a Linux 64b 9.0.2 server which has been patched to APSB13-27 before using UU2 update, up to APSB14-23 running on Java 1.8.0_66 it blows up with the following error trying to render any CF page:


    The server is 100% functional without the hf902-00007.jar file in place, if I put hf902-00006.jar back and leave all other patches it’s fine.

    Is it possible there’s a nice workaround, or, way to get that going – even if it’s unsupported?

  12. Charlie, thanks. 1.7 doesn’t support TLS1.2 which makes some things not work now, cfhttp for instance won’t consume sites that require tls1.2 only. Upgrading to 11 is time consuming and horrifically expensive for a licence stand point. Stuck between somewhat of a rock and hard place!

Leave a reply