Blog

Brad Wood

December 21, 2017

Spread the word


Share your thoughts

As Christmas draws near, remember to pick up batteries for all those toys.  There's nothing worse than a Christmas morning with not enough AA's.  In fact, there's solid evidence that this entire holiday is a ruse to keep battery manufacturers in business.  They're probably kahoots with the peppermint latte guys.  Anyhoo, let's talk quickly about using custom versions of Java with CommandBox.  

Custom Java Version

Some people (who will remain nameless) are on older versions of ColdFusion 9 (you know who you are!) and they are stuck back in the dark ages of Java 1.7.  Other people are already in the future with Java 9 on their machine, but whoops -- nothing actually works on Java 9 yet!  No to worry, we've got a way for you to dial in just what you need.

For the CLI

The core CommandBox CLI needs Java 7 or 8 right now.  Whether you're on *nix or Windows, the CLI will employ several kinds of dark magic to divine what the current installed version of Java is on your machine.  If your default Java version is not what you want and you don't want to change it (or perhaps you don't even have Java installed!) then you can hint to the CLI by simply placing a folder named "JRE" in the same directory as the box binary file.  When CommandBox starts, it looks for this folder and uses it as the JRE if it exists.  Inside the "JRE" folder should be a "bin" folder and the "bin" folder should have the "java" binary.  Double check that if it's not getting picked up for some reason.  You might just have an extra folder nested in there.

For your server

By Default, your servers start using the same version of Java that the CommandBox CLI is using. For people needing to run Adobe ColdFusion 9, or who just want to do some testing on different JREs, you can point each of your servers at a custom JRE and CommandBox will use it when starting the server.

server set jvm.javaHome="C:\Program Files\Java\jdk1.8.0_25"

To set the default version of Java for all the servers you start on your machine, use the global config setting defaults.

config set server.defaults.jvm.javaHome="C:\Program Files\Java\jdk1.8.0_25"

 

Add Your Comment

(1)

Oct 20, 2018 21:40:48 UTC

by Stewart McGuire

Brad, you should make a note that the folder in the /usr/local/bin folder for the JRE in linux should be "jre" not "JRE". I just discovered that. I actually created it as a symlink to my OpenJDK that I just installed along side my 1.10. Now my CommandBox is using 1.8.

Recent Entries

Using CommandBox Docker Images to Perform Bytecode Source Conversions

Using CommandBox Docker Images to Perform Bytecode Source Conversions

There are times when code needs to be shipped in a compiled state. It might be for obfuscation or source protection, it might just because it runs faster that way, without the CFML server needing to compile templates at runtime. It's an excellent use case for production Docker images and code deploy pipelines.

Jon Clausen
Jon Clausen
October 03, 2022
cbElasticsearch 2.3.3 Released

cbElasticsearch 2.3.3 Released

We are pleased to announce the release of cbElasticsearch version 2.3.4. cbElasticsearch is the Elasticsearch module for the Coldbox platform, and provides a fluent CFML API for interacting with, searching, and serializing to Elasticsearch servers.

This release adds full compatibility for Elasticsearch v8.x as well as maintaining support for Elasticsearch versions 6 and 7.

Jon Clausen
Jon Clausen
October 03, 2022
Ortus Will be at Adobe CF Summit 2022!

Ortus Will be at Adobe CF Summit 2022!

4 of our Ortusians will be speaking at CF Summit this year from Oct 3 - 4 in Las Vegas, Nevada. Here are all the details you need to join us and enjoy valuable CFML content to modernize your projects! We are sponsoring the event and will have a booth for you to come by and have a chat with our team!

Maria Jose Herrera
Maria Jose Herrera
September 27, 2022