Really ignorant question.
I have a dev server runn...
# box-productsd
Dave Merrill
06/26/2023, 3:27 PMReally ignorant question.
I have a dev server running ACF 2018 latest and java latest for that cf version, 11.0.19.
As part of originally setting that up back in 2021, CommmandBox was installed.
When I just tried to run it now, with
box versionThis application requires a Java Runtime Environment 1.8.0c
cfvonner
06/26/2023, 4:10 PMDownload the latest CommandBox with JRE for your OS. Replace the
box.exejred
Dave Merrill
06/26/2023, 4:32 PMThanks Carl.
Just to be clear:
• box.exe is on some drive at /commandbox-jre-win64, and I want to replace that with the latest version, yes?
• I'm less clear about the relevant jre. The java cf is using is in a dedicated directory for its java version, but we're not talking about replacing that I assume, right?
c
cfvonner
06/26/2023, 4:33 PMBullet point 1 - yes.
Bullet point 2 - putting a compatible JRE in the same folder as Box.exe will ensure that is the JRE that CommandBox itself will use. It won't impact any installation of ColdFusion, Lucee, etc.
cfvonner
06/26/2023, 4:35 PMIt may be that back when you installed CommandBox originally, you relied on whatever JRE was installed already on your system. With the potential for conflicts with other Java-based applications, it's best to use the "CommandBox with JRE" download and place the JRE in the Box installation folder so that CommandBox is guaranteed to use that JRE.
cfvonner
06/26/2023, 4:39 PMAlso, you can specify in your
server.jsond
Dave Merrill
06/26/2023, 5:53 PMWe remove the system jre on all servers, and use one specifically installed for cf, which it's explicitly configured to use. That way we only have to keep that one up to date w security fixes, our security audit software doesn't yell at me about old jres, and it's super clear which one is involved.
I already checked server.json, it's an empty object, so putting the new jre in the folder w CommandBox seems simple and clear. There's no issue with that not being the same one cf uses, or even the same version, yes?
c
cfvonner
06/26/2023, 5:59 PMNo issues.
d
Dave Merrill
06/26/2023, 6:57 PMThank you sir 🙂
b
bdw429s
06/27/2023, 4:56 PM@Dave Merrill I'm curious where that error came from. CommandBox proper doesn't even have any version checks I don't think outside of a min Java check perhaps.
bdw429s
06/27/2023, 4:56 PMWhat OS are you running this on? *nix? Windows?
bdw429s
06/27/2023, 4:57 PMThe Launch4j wrapper we use has its own checks-- I just looked and I do have this in place in our build that controls the launch4j behavior
Copy code
<jre path="./jre/;%JAVA_HOME%;%JRE_HOME%;%JDK_HOME%;%PATH%" minVersion="1.8.0" maxVersion="15.0.0" />bdw429s
06/27/2023, 4:57 PMThe irony is I've been testing Java 17 locally with box on windows and I never had any issues
bdw429s
06/27/2023, 4:58 PMI'm really curious just what version of Java was getting used when you encountered that error and where the actual message came from that you saw.
bdw429s
06/27/2023, 4:58 PMIf Java 11 was the only jre on the machine, this should have been no issue at all!
d
Dave Merrill
06/29/2023, 3:00 PM@bdw429s How would I find out the java version being used by the cmd line when I ran
box version<jre path=...b
bdw429s
06/29/2023, 5:48 PM@Dave Merrill The
infobdw429s
06/29/2023, 5:49 PMStarting box with the
-clidebugbdw429s
06/29/2023, 5:50 PMdoens't include any mention of "java" or "jre".a folder called
javajre Copy code
./jre/2 Views