Warn logging for complex values in session scope

We’re running a FW/1 app and have noticed, in the latest version of Lucee, the following logging:

"WARN","XNIO-1 task-2","12/18/2025","12:51:03","scope-context","the session scope contains complex values, Lucee cannot proper detect changes in the values and because of that updates the storage with every request.; "

I believe it’s the result of this commit.

I understand the idea, but the issue, from our perspective, is that it’s spamming the logs with warnings - 38 in the past 15 minutes - 414 in the past hour. It’s being logged on every request.

We know that structs are being stored in the session scope. FW/1 does this, even if we didn’t. We’ve accepted it, and don’t need to be reminded with a warning message on each session request.

I’m not sure what the best solution is - I’d like to be able to toggle this logging off - it feels excessive.

Don’t forget to tell us about your stack!

OS: Docker container with eclipse-temurin:21.0.8_9-jre-noble as the base image (so, Ubuntu)
Java Version: 21
Lucee Version: lucee-light@6.2.4+21

2 Likes

As a workaround, you can reduce the log noise by going to the Lucee Admin → Logging section and setting the Application log level to Error. This will prevent these warning messages from being logged on every request.

1 Like

Thanks @cfmitrah - we use warn logging intentionally throughout the app, so that would silence actual logs we’re interested in.

1 Like

@mjclemente i understand your problem.
The main reason for his log entry is that we did a limited fix in Lucee 6, because Lucee 6 is in maintenance mode. We do not have this log entry with Lucee 7, because Lucee 7 now can proper handle complex values.

I can make an env var you can set to disable this log entry.

Thank you!

We’ve got updating to 7 on our roadmap.

Huge shoutout of appreciation to you and the Lucee team for all your work on this. Cheers!

i have created an env var to disable it, here the ticket
https://luceeserver.atlassian.net/browse/LDEV-6026
here the documentation for it

3 Likes

Thank you - we rolled this out today! All good here. Appreciate that!

1 Like