Refreshed CF2018 installer includes Java 11, and more

April 5, 2019
ColdFusion troubleshooter
Legend 57 posts
Followers: 51 people
4

Refreshed CF2018 installer includes Java 11, and more

ColdFusion troubleshooter
Legend 57 posts
Followers: 51 people
April 5, 2019

Did you know that the ColdFusion 2018 installer was “refreshed” on Feb 12, 2019? Its primary change was to include Java 11, as the original installer from July 2018 shipped with Java 10. It also comes pre-configured with CF2018 update 2. Even so, there are subsequent updates to both CF and Java that you should consider. I also share here info on identifying the installers, and possible issues to consider going forward, given the existence of these different installers for the same CF version.

How it’s news you could have missed

If you hadn’t heard about this updated installer, it would was easy to miss the news in the flurry of CF updates which had been released the same day (for CF2018, CF2016, and CF11), as well as more the next week and yet a week later. While there were indeed Adobe blog posts about each of those updates, I don’t find that there was a separate Adobe blog post about the refreshed installer, which is why I’m writing this.

Instead, the new installer is mentioned only briefly in the page which lists all ColdFusion (2018 release) updates, as indicated between the news of updates 2 and 3:

ColdFusion (2018 release) Update 2 – installer refresh

ColdFusion (2018 release) Update 2 installer refresh (release date February 12, 2019) contains support for Java 11

So to be clear, if you do download (or have downloaded) CF2018 from the Adobe CF site after that date, you will get the new installer.

Some further updates you should still consider

Though the installer is “updated”, it can no longer be considered to “completely updated”, in terms of both CF2018 and Java.

First, as I noted above there was another update to CF2018 since then: Update 3, on March 1, which included an important security update, so you will want to apply that also.

Next, the JVM which the new installer comes with is version 11.0.1, and since then there was the newer 11.0.2, which you should consider. And yes, Adobe always supports you moving to the latest point release of a given Java version (like 11.0.2), as long as that CF version supports the major version (like Java 11, as CF2018 does after update 2). As for info on updating CF to use a new Java version, there are many resources from Adobe and others, including a recent blog post and video walking through the process from Pete Freitag.

How would you know if you have the refreshed installer?

If you may find that you already have a CF2018 installer (or if a colleague points you to one downloaded onto your server/s), you may wonder if it’s indeed this latest one or not. Some good news with the Windows installer is that if you right-click the file and choose “properties”, then the “details” tab, it will report under “File Version” that it’s “2018.0.2”. The original installer would indicate “2018.0.0”.

As for the Linux, Solaris, and MacOS installers, there is no similar “file version” information available (even if downloaded to Windows servers), so we would need to rely on checksums or file sizes to distinguish the two installer versions. For now, Adobe has not published either of those. Perhaps they or others will report here the values of the new files, if not also the old ones (though of course we really need a trusted authority to report such values).

Some things to watch out for, going forward

Finally, I will note that there are a couple of things we should watch out for going forward, based on past experience when multiple versions of a given CF installer existed.

First, it could be confusing as some folks won’t even realize there are two versions of the CF2018 installer, and they may think they are installing the later one when they are not, because they or someone else downloaded it prior to Feb 12.

Second, while those with the old installer had the option to move to Java 11 (after applying update 2), those who install CF2018 with this refreshed installer will instead automatically get Java 11 implemented. And though Java 11 is indeed formally supported by Adobe, we should acknowldege that it’s indeed early days with respect to any possible issues that may arise with folks running CF on Java 11.

Third, we should also consider that Adobe has in the past reported with a given refreshed installer that it “only had changes to xx and yy”, when it turned out instead that some other perhaps “little change” was slipped in. That too could cause confusion, if folks don’t know which installer version they used, or don’t clarify that when perhaps asking questions or discussing challenges.

In this last section I don’t mean to throw a wet blanket on the new installer. Indeed, I’m sharing the news of the new installer so that people ARE aware of it, and the good news that it DOES implement Java 11 and update 2, out of the box. But I also wanted them to know that they still need to update it, and that there might be this potential confusion on matters just mentioned, as we go forward with the two installers existing.

That’s the way it is, April 5 2019, at least

Finally, I’ll add that all this was so as of the date I am writing this, April 5 2019.

There will surely be more updates to CF and to Java over time, and there could even be a reason in the future that yet another CF2018 installer would be released. This happened with CF2016, which had its original installer, then another in December of that year to bundle some updates, and then yet another a few months later to add support for Windows Server 2016.

At least we can know that a new installer won’t be needed for Windows Server 2019, as that support was bundled with Update 2, along with support for Solaris 11.3, OSX 10.14, and various updated versions of web servers and databases. See that update 2 technote for more. And let’s give a cheer for Adobe being ahead of the game on Windows Server 2019, whereas with Windows 2016, Windows 10, and even Windows 8 (and various versions of macOS) there were often months of lag before things would work for those who moved to those updated OS versions quickly.


For more blog posts from Charlie Arehart, see his posts here as well as his posts at carehart.org. And follow him on Twitter and other social media as carehart.

Comments (4)
2019-04-19 06:47:14
2019-04-19 06:47:14

Hey Charlie,

Sorry for the late reply and sorry for posting that here as I jumped the gun on the Java 11 title in the heading and my 2016 issue. Well as we discussed in DC, it appears the issue was caused by a flag I had in my jvm.config. The flag causing the issue was this one “-Dcom.sun.net.ssl.enableECC=false”, once I removed it, the cfhttp connection was able to complete the SSL handshake and work 🙂

Like
(1)
>
Giancarlo Gomez
's comment
2019-04-19 12:00:28
2019-04-19 12:00:28
>
Giancarlo Gomez
's comment

Thanks for the update, GC.

Glad you got it working, and hope the info you shared may help others.

Like
2019-04-09 17:41:52
2019-04-09 17:41:52

Giancarlo, that’s a little off-topic, as this was about CF2018 and its latest installer having Java 11 built-in, but perhaps you’re fearing your problem could affect those on CF2018 who go to Java 11.

I’ll say I’ve not heard of that issue before, but again it’s early days for use of CF with Java 11. Even so, here are a couple of other things to consider, before we may presume it’s inherently a bug.

First, try deleting the underlying cfclass file of the template doing that cfhttp. It may be calling libraries in a way it would not, if the code was recompiled by CF for Java 11. When folks move CF from using on major Java version to another, I recommend they stop CF and clear out that cfusion/WEB-INF/cfclasses folder (or rename it, and CF will create it anew on restarting).

Second, I presume you just applied one of those latest updates from Feb or Mar (8, 9, or 10) which added Java 11 support to CF2016. You don’t say. You can’t use Java 11 with CF2016 if you’re still on update 7, that does NOT formally support Java 11.

Third and finally, do make sure also that you had no errors in applying your last update, whichever of those 3 it may have been. For more on how to do that, see my post, https://coldfusion.adobe.com/2019/03/problems-applying-cf-update-check-first/.

Even if you “don’t plan to go to Java 11 again anytime soon because of the problems”, you can (and should) still check out that last point. But if you can try the first one (and confirm the second), I’d be interested to hear if it may fix things for you.

Like
2019-04-09 04:07:28
2019-04-09 04:07:28

I will comment that using Java 11 on ColdFusion 2016 caused an error with CFHTTP connecting to Google’s Captcha Service. I would get a “Connection Failure: Status code unavailable.” error. I reverted back to the previously used JDK of 1.8.0_161 and it started working again. The version I am referring to is 11.0.2 found @ https://www.adobe.com/support/coldfusion/downloads.html.

Like
Add your comment