Hey @zackster cheers for the really through release notes you are doing now (eg: https://dev.lucee.org/t/lucee-5-3-9-141-stable-release/10219)

Found an interesting performance bug: using

isImageFile( url )

is several times slower than cfhttp + isImageFile( tempFile ) : https://luceeserver.atlassian.net/browse/LDEV-4177 so much so that it appears to request the url multiple times

why does cfdirecotry tag support specific regions while using S3

it can only be EU, US or US-West

part of me was hoping lucee-builder was like cf-builder, but open source... but most of me knew it wasn't from the description on github, side note, anyone done anything with tree-sitter and cfml ?

i want to use the charts on lucee admin in my local code i was checking where i could find it i looking at this https://github.com/lucee/Lucee/blob/6.0/core/src/main/cfml/context/admin/chartProcess.cfm is thus the right location

@gert I was looking around at the rasia site today, talking up lucee and Rasia support to my team (trying to get them off acf) and I noticed the blog has'nt been updated since 2018. Also not sure whats the status of the argus cache project, but looks like the ssl cert has expired on the site.

Hey Steven, let’s take this to DM 🙂

But true, we haven’t blogged in a while. Thank god it’s because we’re VERY busy 😄

Thats always a good reason

What's the current favourite alternative to the Oracle JDK for Lucee install these days?

We test and distribute using https://adoptium.net/temurin/releases/?variant=openjdk11

anyone interested in trying out some native arm docker images (think apple M1/M2 arch) test images are up https://dev.lucee.org/t/native-lucee-arm-docker-images-apple-m1-m2-support/11044 thanks to @justincarter for doing the hard yards on this

For a

<cfquery>

call that causes a DB error, is there any way of getting back the exact SQL string that was sent to the DB? In the returned exception all the param values have been inlined into the SQL (eg: I see

SELECT * from tbl WHERE col = 'param value'

not

SELECT * from tbl WHERE col = ?

(and then a separate struct of the param values that were passed). Reason being... the error I am getting is with how Lucee is passing the param values, and I can't troubleshoot it if I can't see what it's passing. I could likely get it back from the underlying JDBC exception, but Lucee swallows that (see https://luceeserver.atlassian.net/browse/LDEV-3738). Am just wondering if there's any other way. The issue is that somehow an SQL string /

<cfqueryparam>

combo I am getting is somehow passing more params than it is param markers (ie, the

?

in the SQL string), and I'm trying to work out why. Error is

Parameter index out of range (3 > number of parameters, which is 2)

The SQL string is getting munged by some CFWheels stupidity, but I am trying to work out how I'm not just getting a SQL syntax error (which I should), rather than this param count mismatch. To recap, the question is just this: "is there any way of getting back the exact SQL string that was sent to the DB?" The rest is context.

Hello folks, wondering if anyone is actively using lucee fuseless (AWS Lambda) and has installed an extension into the JAR

looking to connect to an S3 bucket

@zackster I can't find anything about these query listeners other than this: https://southofshasta.com/blog/cfcamp-notes-on-railo/#:~:text=CFquery%20listener%3D%22%23listener%23%22 https://www.google.com/search?q=lucee+%22query+listener%22 Should I take this to mean they are not documented? I searched for a few things. Both in Google and in yer docs.

Has anyone seen any CORS related issues between Lucee 5.3.9.141 and 5.3.9.160? Running a javascript app on my local dev machine connecting to a local Lucee server (Commandbox) I am seeing random CORS errors when making requests (Taffy API). I can hit the same api endpoint 5 times and 1 out of the 5 will return a CORS error when on Lucee 5.3.9.160. If I simply stop the server and then start again with Lucee 5.3.9.141 no more CORS errors. It is happening intermittently on most of my API endpoints. I recently deployed the API to AWS with Lucee 5.3.9.160 and started seeing the same random CORS errors - reverted back to 5.3.9.141 and they are gone. The only change I am making is between Lucee version .141 to .160.

Does anyone know if there was a bug ticket or a fix for stored procedures getting cached without the named params? We have a couple stored procedures that have multiple result sets and somehow it gets cached in Redis without the result sets even though the result sets always return a value.

I have two servers, that should be configured the same (but perhaps are not?). They both worked a week ago. When I checked today, one of the servers is trying to serve files from the root of the C: drive! This only happens with .cfm files. If I browse to an image or html file it gets served from the correct directory (C:\inetpub\wwwroot\mysite). So I think the problem is in my Lucee config somewhere. This is a new server that hasn't been put into production yet. It's running the latest Apache 2.4, latest Tomcat 9, and latest appropriate JVM. Lucee version is 5.3.8.201. Any ideas what I should be checking next? As I said, this is one of a pair of servers, and the other is working correctly. I've compared the httpd.conf and server.xml files and the only differences are where they should be (IPs and such). Here's another clue, I see this error in my log, the app is trying to load it's config from the root of the C drive.

file or directory [<C://config/ColdSpring.json>] does not exist

It's like there is a mapping pointing / to C:\, but I have checked and I don't see any odd mappings.

I am attempting to control caching on component functions, in Lucee latest, utilizing

cachedWithin

directive by wanting to use an application or session scoped variable that is utilized by specific functions. Any change in the variable will then make a sweeping change to all functions utilizing cachedWithin with this variable. I even attempted to set a variable inside like so

cachedWithin = createTimeSpan(0,0,variableHere,0)

, but every attempt leads to an error needing a literal value. Is there any way to create a cache on functions with a variable? Is there a reason why we cannot use a variable on a

cachedWithin

directive?

Updated Compress Extension and CVE advice https://dev.lucee.org/t/compress-extension-1-0-0-12-zip4j-2-11-2-cve-2022-24615/11078

Hey there, Does anyone have a docker image that has been setup for building/testing Lucee on Windows host? If not that's fine... I'll work through setting one up myself... I have all the prerequisites, setup. Lucee BUILDS fine - but I seem to be having errors with the tests. It would seem I have a permissions issue - bhut that is weird - because I am running

cd loader
mvn test

from a CMD prompt that I started with "Run as Administrator". So before I went into a rabbit-hole - I thought I would ask if there was something already setup - that I could use. Thanks!

We just updated our app image from 5.3.9.133 to 5.3.9.160, and got an unexpected bonus: Way fewer vulnerabilities in Lucee's dependency set now. (I've checked the ones in 5.3.9.133, and none seemed to be ones that Lucee could actually mitigate as they're known & unfixed issues in the OS / common libs the underlying OS image uses etc)

What is the best way from an admin to force a logout of all users to an application (effectively forcing them to re-login at their next request)? The users are stored in J2EE sessions. Currently playing with this code, but is it safe/wise? Are there better ways to do it? FWIW, we're probably only talking about just a couple hundred users logged in at any given time.

var userSessions = createObject( "java", "coldfusion.runtime.SessionTracker" ).getSessionCollection( application.applicationName );
userSessions.each( ( user ) => structClear( userSessions[ user ] ) );

Heaps up, anyone feeling like doing some pre RC testing on 5.3.10.70, now's your chance. (early testing really helps us make RCs better) https://dev.lucee.org/t/5-3-10-rc1-coming-up-soon/11094

We had a weird glitch this morning with our lucee app server, I wonder if this has hit anyone else or anyone has an ideas. We build our image from

ortussolutions/commandbox:jdk11-alpine

with lucee-light@5.3.9.133, the build pipeline downloads the lex extensions we use like s3, json, jdts, etc directly into

${BOX_SERVER_APP_SERVERHOMEDIRECTORY}/WEB-INF/lucee-server/deploy/

so they are warmed up and deployed, then each instance doesn't have to download the extensions from the lucee release server. This has been running basically fine like this for a couple years. The build that got deployed last night started throwing the error:

S3 uploadFormFile failed The OSGi Bundle with name [s3.extension] is not available in version [0.9.4.155-SNAPSHOT] locally (/app/server/WEB-INF/lucee-server/bundles) or from the update provider (<http://release.lucee.org>), the following versions are available locally [0.9.4.154, 0.9.4.154].

We didn't change what version of the s3 extension we use (0.9.4.154), or what version of lucee we use, it was just a code push. The only thing I can think that changed between docker builds is the base docker image, but even then I can't figure why that would make lucee v5.3.9.133 thinks it needs a different s3 extension version to run? This has happened twice before, in exactly the same way. The fix for the problem was to bump the s3 extension to the snapshot release 0.9.4.155-SNAPSHOT, then lucee was happy and working the same. Its a bit unsettling when this to issue happens, I've come to expect docker images to be very consistent, I wouldn't expect this type of compatibility issue unless I was changing the lucee server. Next steps is we're looking to change our build process from lucee-light to lucee regular, hoping the bundled extensions are more consistent, has anyone else run into this issue?

I was ferretting around in the Administrator object (and server scope) for a way to resolve

{lucee-config}

to an actual file system path. Reason: the logging info one gets from

Administrator.getLogSettings

lists the log paths as - eg -

{lucee-config}/logs/exception.log

. Which is lovely, but about as useful as a chocolate teapot if I want to actually access the file. Anyone know how to get the value of

{lucee-config}

? And for bonus points:

{lucee-server}

and

{lucee-web}

, which are also used as placeholders in various other settings. This seems to be obvious functionality for Administrator, given it uses these values so much..? Cheers.

Am I right in assuming there is no support for .NET object creation in Lucee (5.3.9.160)? ... since I'm getting a Function [CreateObject] with [type .net] is not supported/implemented when I try it. Or is there something I am missing? thanks!