Our final Release Candidate is up for 6.2.1
https://download.lucee.org/changelog/?version=6.2
Huge shout out to everyone who’s been testing and reporting back success and bugs!
For the best results, while in place upgrades work, you’ll get the best performance running on Tomcat 11 and at least Java 21, i.e. speedy virtual threads etc
Hello.
My configuration is centos 7 with adoptopenjdk 11
What java version can I update on centos 7?
Do you have a guide for the update?
Thank you.
I the link to the guide is in the post?
A guide for upgrade adoptopenjdk on Centos.
I don’t know what is the latest version of java supported by centos 7
How old is your install? What version is your loader / tomcat? The 6.2 loader has improvements which solve some other problems and performance issues
There is a jre folder under /opt/lucee which you can just switch out, stop lucee, switch the jre folder and restart
As for if it will work in centos 7, yeah probably but I’m just a lucee guru, just try it or ask uncle google
But you won’t get the best performance without tomcat 11, hence my suggestion of a fresh install, which also avoids problems some people have had with in place upgrades.
Lucee 6.2.0.321
Loader Version 5.3.4.80
Servlet Container Apache Tomcat/9.0.102
Java 11.0.6 (AdoptOpenJDK) 64bit
OS Linux Centos 7 (3.10.0-1062.18.1.el7.x86_64) 64bit
Everything works great, and I would like to avoid doing any damage.
I should change the entire server soon, I would like to get a new machine with almalinux, use all the latest versions of java, tomcat, etc., but in the meantime I am undecided whether to update the current one.
Thanks always for your precious help
No worries, glad it’s all working!
Consider updating the loader to 6.2.0.321 tho, 5.3.4 is a bit old
Thanks for all your work on this, and for all the time you spend in these forums helping folks out!
I was hoping that LDEV-5457 would be addressed before the official release - any chance it’s gonna be included?
Not being able to authenticate with the AWS Java SDK is probably going to be a blocker for us, unless we can put together a workaround.
Out of curiosity has anyone been able to get lucee to run on tomcat 11 on macOS?
I’ve installed openjdk 21via homebrew, gone through various steps with terminal to make sure the JRE_HOME path was pointing to the right source and got TC11 to work.
However, I’ve tried a few different things to try and get Lucee 6.2.112-RC to work and I have had no success yet.
I tried deleting the TC11/webapps/ROOT folder and replacing it with the lucee.war app renamed to ROOT.war and had no luck. Also tried just adding the lucee.war file to the webapps directory. Navigated to localhost:8081 and the tomcat homepage popped up no issue, but navigating to localist:8081/lucee gives server not found.
I’ve started and stopped TC11 in between iterations to make sure things were clicking the way they are supposed to.
Any ideas out there?
Did you try Lucee express? https://cdn.lucee.org/lucee-express-6.2.1.112-RC.zip
Express is simply the Tomcat distribution with all the required additional config and jars, plus the lucee.jar in lib/ext
simply unzip and run ./startup.sh?
@Zackster If we install Tomcat 11 via its own Windows installer, am I correct that we only need to add the /lib/ext folder with those 3 javax jars (found in the Lucee Express bundle you linked to) in order to run 6.2.1.112-RC? You mentioned in an earlier post “You’ll need to manually add the javax servlets to Tomcat 11” but I did not see any “config” for that - just the presence of the lib/ext folder itself.
Of course, we need to diff the changes in the web.xml and modify those appropriately as well.
We manually add that the lib/ext folder to the tomcat/conf/catalina.properties, thus indicating by convention it’s not part of tomcat distribution.
For Lucee Express we put that under tomcat/lib/ext as there’s no top level folder lucee/lib
Any reason why you’re not just using the Lucee Windows installer?
https://cdn.lucee.org/lucee-6.2.1.112-RC-windows-x64-installer.exe
I hadn’t but I did give it a go this morning. Unfortunately it didn’t fire up for me, which is to bad cuz I love mucking around with these things. I’ve been joneson to upgrade tomcat for awhile, but haven’t been able to work it due to Lucee not cooperating.
I’ve never done a deep dive on trying to make Lucee and any versions of tomcat > than 9. Gotta get some work done today, but I’m peeked enough that I’m going to continue to investigate. If I come up with the solution, I’ll make sure to post it.
Thank you!
We never used the installer because, historically, it always seem to lag the Lucee release cycle (it appears that’s less of an issue now).
Also, we do not use Boncode, which I think is default?
Last, we have Lucee installed in a different directory and have other applications that monitor and ingest things like logfiles, etc. that point there.
These are all easy enough conventions to do away/change with, but like the idea of keeping things separate and being able to update each individually.
it’s all automated these days, took a lot of work but it was worth it
the installer is pretty configurable these days, let me know if there’s something missing you’d need
Boncode is completely optional, that said, thanks for the reminder, I needed to update the installer to bundle the latest version
Any idea on when 6.2.1 will be released? I was trying to see what tickets were still being worked on, but couldn’t quite tell. Thanks!
