I've discussed the matter of JVM updates relative to CF--and several important things to consider--in another post I did for the last update (in April), on the Adobe CF portal: https://coldfusion.adobe.com/2019/04/updates-available-java-8-11-apr-16-2019/. In that, I cover topics such as:

• Which Java can I use with the version of CF I have installed?
• Am I really able to use Java 11 (and Java 8 updates after 202) in production?
• Where can I download the Java updates?
• How do I update the Java that CF is running?
• What if I have problems updating the Java that CF uses?
• What if I have problems applying the CF update (so that I can run Java 11)?

All my answers there are as relevant now as they were then. (That said, whereas that update offered two variants for Java 8, as 211 and 212, this update has only the one, 221.)

Finally, note that as of this writing (5p Central on the 19th), the JVM installers and files are NOT available on the Adobe CF downloads page, section on JVM files. If past experience is a guide, it may not appear for several days. (See my comments on whether that should "matter" for you, in the aforementioned blog post.)

And as I explain in the post, I have other past blog posts that can help if you will be trying the JVM update yourself, or I can help through my troubleshooting consulting.

These all-new ones will focus on Troubleshooting with FusionReactor and are geared toward helping folks new to FR--or perhaps experienced but a bit bemused by its many features--to better understand how to use it to troubleshoot problems in your app server (CF, Lucee, or any Java server).

The parts in the new series (with links here to register directly to attend) will be:

[....Continue Reading....]

[....Continue Reading....]

The first problem was introduced in the CF2016 installer released in Dec 2016, and any after that, where Adobe has literally removed the library used for the calendaring, but you can add it back, as I discuss below. (If you install or installed CF 2016 from the original installer in Feb 2016, you won't see this problem as it wasn't removed then.)

The second problem was introduced in those two named updates, and was fixed in the very next updates (CF11 update 13 or CF2016 update 5). And of course, this could also happen if you're moving to CF11 or 2016 for the first time, and someone else had "fully updated" those to that update level before you started testing against it.

If you'd like to know more, read on.

[....Continue Reading....]

Unable to connect to the Java VisualVM Plugins Center because of Server returned HTTP response code: 503 for URL: http://www.oracle.com/splash/java.net/maintenance/index.html

There is a solution.

TLDR: the quick answer is to change the URL used by the tool (Tools>Plugins>Settings) to use a new URL, such as https://visualvm.github.io/uc/8u131/updates.xml.gz.

For those who'd appreciate more detail, read on.

[....Continue Reading....]

[....Continue Reading....]

So here I present what I feel are the 100 (technically, 105) most interesting/useful posts made there over the past 3 years (2014-16), offering information about CF and CFML which should be valuable to readers for years to come.

[....Continue Reading....]

[....Continue Reading....]

[....Continue Reading....]

In this post, I want to elaborate on one more common mistake. Well, mistake may be too strong word. It's about a default option when you run a Java JDK installer (see the other post for more on JDK vs JRE options).

In short, I make the case here for why you should NOT let the JDK installer implement its "public jre" option.

[....Continue Reading....]