We'd love to hear some feedback about 6.2.1

[Zackster]

How is everyone going with 6.2.1? We have worked really hard on making it a solid release, the Lucee team would love to hear some success stories!

How are all the performance improvements we’ve done performing for you? Are your servers using less memory, running faster, have you started using the new java integration?

Show your love by starring Lucee on GitHub

GitHub - lucee/Lucee: Lucee is a high-performance, open-source CFML...

[noursecode]

Sure… We are now using Lucee 6.2.1 in production and are very happy with the results. So far we find Lucee solid, reliable, and fast.

From monitoring our servers, we noticed Lucee handles requests quickly without eating memory or CPU… on both smaller and larger VMs.

Easy to deploy too, we now use Lucee light-nginx docker images that handle URL rewrites and offer customizable Lucee extensions all inside a smaller package.

From our perspective, Lucee 6.2.1 is the best yet.

If you are a CF, PHP, Ruby, Node, or GO developer, it might be worth taking a closer look.

You get rapid development without the need of AI, along with a high-performance, Java-powered runtime.

[Michele_Scaletta]

It works great, and after updating the loader to the latest version and java to 21 it uses less memory and less cpu and is faster.
You have done a great job

Version Lucee 6.2.1.122
Loader Version 6.2.1.122
Servlet Container Apache Tomcat/9.0.102
Java 21.0.7 (Eclipse Adoptium) 64bit
OS Linux (3.10.0-1062.18.1.el7.x86_64) 64bit|

[thefalken]

Until https://luceeserver.atlassian.net/browse/LDEV-5536 is sorted, I don’t want to try 6.2.x (we have 6.1.x in production[0] in some places that have already taken the leap from 5.x).

I’m not sure what version of Lucee the issue was found in.

Loading the wrong CFC is quite the issue - for instance we might have several versions of a site running under different domains and web roots, so the CFC path is the same, and loading a different version of code from the same path in some other root would be terribly hard to debug…

[0] Under Docker, using FROM lucee/lucee:6.1.y.x-nginx

[Zackster]

@thefalken We just rolled out a fix for the single mode problem

Lucee 6 createObject() returns instance from another project

Please try 6.2.2.11-SNAPSHOT or 7.0.0.226-SNAPSHOT, we have deployed a fix for this problem

[Zackster]

Interacting with Java Libraries in Lucee 6.2

We are just getting around to Lucee 6. Thank you thank you thank you thank you! I spend almost all of my time integrating with third-party systems. We already use maven to populate the libs folder and then either write things in java and bundle them into a jar or end up using Java in Lucee with all the unnecessary boilerplate. Before that it was using Java loader and having it autoload entire firectori a if jars that we downloaded. This is beautiful and simple and I’m so happy about it. Than…

[quetwo]

At this point, I’ve been able to move over my most critical applications that my team manages, including one that 911 emergency dispatchers rely on to locate folks in real-time.

We are deploying apps within containers (-zero image) and the improvements made in the last few versions have been great. Memory use is down, responsiveness is up, CPU use is down and the stability is up there with what we expect. And with the team jumping to the latest Java and Tomcat versions, the CVE reports are in good shape too.