Announcing Lucee 5.3.2-RC (

Greetings, Lucites! Time for the second Lucee release in the past 10 days!


Astute observers know that over the past year+ our releases are now spaced farther apart. However, due to the extra work that went into the final release of 5.3.1 (more testing, 2 Release Candidate periods, more regressions found and fixed, etc.), that release got pushed into this week’s 5.3.2 Release Candidate. Read on for all the details!

(Chemical formula for Poly(methyl methacrylate), sometimes commercially known as Lucite; Or, sort of looks like a Lucee developer on Monday morning :rofl:.)

Today we’re announcing Lucee 5.3.2-RC (, following the completion of the March sprint. As we noted when shipping the final build of 5.3.1, the 5.3.1 development cycle was, overall, long and loaded with development work! Still, we stuck with our plans for the March sprint, in order to stay on schedule. Right on the heels of the busiest-ever development cycle with 5.3.1 (first-ever 3-digit build number–!), today’s 5.3.2-RC covers another 64 tickets! Here’s the summary:

Ticket Summary
LDEV-2217 CFFEED returns struct with empty keys, bonkers content
LDEV-2216 Error in RamCache run can turn into CPU hog
LDEV-2211 cfdbinfo is slow with MySQL Connector/J 8.0.x driver
LDEV-2198 AxisFault when return object is complex cfc
LDEV-2196 XmlSearch returning empty arrays after update
LDEV-2195 extend “org.osgi.framework.system.packages” with “”
LDEV-2194 function ListFindNoCase in precompiled code no longer works
LDEV-2192 Modern.cfc addresses js function as cfml function
LDEV-2191 ListLast no longer works for old Lucee archives (.las)
LDEV-2183 debug-template Classic.cfc with error after update ro
LDEV-2175 When using the extract() method and a wrong argument, a false error message appears
LDEV-2152 Recursive directoryList Sort is Depth First instead of Breadth First
LDEV-2136 Auto installed extensions don’t follow redirects
LDEV-2129 Calling canonicalize() with an empty string returns NULL
LDEV-2126 GetTimeZoneInfo() include SHORT display name in results, i.e. PST
LDEV-2114 IsIpInRange() returns incorrect false values
LDEV-2105 Lucee does not forget templates deleted
LDEV-2104 allow queryformat=struct when requesting data from a CFC
LDEV-2100 LuceeAjax.js does not bind empty values
LDEV-2099 LuceeAjax.js does not correctly encode curly braces in cfajaxproxy JSON arguments
LDEV-2095 function extract only supports zip and tar
LDEV-2084 query.cachedAfter default value for query.cachedWithin
LDEV-2083 FileGetMimeType() for .m4a throws java.lang.NullPointerException
LDEV-2080 Performance Degradation with struct.get
LDEV-2077 Lucee 5.3 is able to hang on Linux, and have connection failures on Windows under concurrency
LDEV-2068 listFirst, listLast changed default behavior for empty fields in 5.3
LDEV-2066 add possibility to block variable usage within cfquery
LDEV-2056 Closures lose scope when using dynamic proxy
LDEV-2055 mapping-tag no longer works
LDEV-2052 overwrite=true no longer works in cfzip action=unzip
LDEV-2051 import not working for application component mappings
LDEV-2048 datasource logger fails with big data
LDEV-2047 flying saucer (PDF) throws error: Attribute page is not allowed for statement document
LDEV-2046 structGet() incompatibility with ACF
LDEV-2043 writable cgi scope case sensitive
LDEV-2032 Collection disappear after restart of lucee
LDEV-2029 cfajaxproxy extension doesn’t create proxy
LDEV-2028 cfajaxproxy not supported in 5.3
LDEV-2014 CFEXECUTE arguments does not properly handle arrays
LDEV-2008 scheduled task errors when shutting down tomcat
LDEV-2005 GetBaseTemplatePath() errors in JSR-223 context
LDEV-1990 GC Overhead limit exceeded with debugging enabled in 5.3
LDEV-1989 CFZIP: add support for password and encryptionalgorithm attributes
LDEV-1953 Datasource JDBC Type 4 driver mysql lucee admin page is wrong on some features now
LDEV-1951 scheduled tasks shouldn’t stop running after an exception
LDEV-1938 datasource specific ORM settings not possible in Lucee
LDEV-1937 ORM Dialect in Application.cfc prevents multi datasource/multi dialect
LDEV-1931 cfdbinfo type=“tables” error on MySQL driver 8.0.11
LDEV-1918 Assigned connection from the pool may change during runtime of a request
LDEV-1899 Cannot see Lucee’s console messages for debugging in JSR-223
LDEV-1781 Resizing “large” images is slow and consumes a lot of memory
LDEV-1763 Tomcat cannot be stopped if there’s a DirectoryWatcher EventGateway
LDEV-1664 update cf module in folder caused error: class redefinition failed: attempted to change the class modifiers
LDEV-1643 RamCache grows without limits, eventually filling the heap
LDEV-1624 this.javasettings - support OSGi bundles
LDEV-1501 SOAP WebServices Type Mapping issue #2
LDEV-1399 isInstanceOf Performance Degradation
LDEV-1304 CFQuery needs a CacheAfter attribute to match ACF
LDEV-973 CFHTTP and ESAPI encoded url’s
LDEV-908 EntityLoadByExample with unique argument fails with Can’t cast Null value to value of type [Component]
LDEV-884 DateDiff with a datepart of “w” (Weekdays) gives the number of weeks between two dates instead of Weekdays
LDEV-640 ScheduledTasks can burn up TCP connections
LDEV-380 Sometimes CFTHREAD cannot join with other CFTHREAD of same page
LDEV-56 CFCATCH does not support NAME attribute

It’s available now at the downloads site. Thanks in advance for as much testing and feedback as you can muster!

5.3.2 will become a final release at the beginning of May, and then next up on the development docket is the May sprint, which will produce Lucee 5.3.3-RC. Still room for your favorite ticket(s), so as always keep up with ticket comments, upvoting, etc.

Thanks for listening!

Patrick, Lucee Product Manager


Man, I thought it was a two-headed stick figure fighting itself… :laughing:


I think its used for preserving food…

Well done Team!

Can we get a separate thread for 5.3.3 / May Sprint requests/feedback?

Good idea Zac. I’ll get that going now.

Good morning,

The “fixed tickets” list contains a ticket that is not fixed but is erroneously marked as fixed on the tracker. We have submitted PRs for this and a related issue and commented that the “deployed” fixes are not fixed, but received no response.

I appreciate that the subject area (old CF compatibility tags) is very mundane and of limited use, but having gone to the trouble of fixing these issues and submitting those fixes to Lucee, we would have no objection if our fixes were rejected in favor of a different solution; or if the whole subject were deemed not worthy of attention and ignored. But marking them as fixed when they are not and then including them in a release announcement shows poorly, not to mention taking up a lot of time when we go and remove our fixes from our Docker build process only to find that we have to put them back.

(the submitted fix also takes care of a ticket not listed above, which is

At any rate, 2100 should not be marked as deployed or appear in this list.

1 Like

Hi @Samuel_W_Knowlton. Thanks for the heads-up. Upon quick glance, I can’t figure out what’s going on here, so let me discuss with the development team, and we’ll get back to you.

@micstriit @isapir @cfmitrah

Has anyone from the community been testing this RC?

I’ve been mostly sticking as usual to testing snapshots

Hi @Samuel_W_Knowlton. Following up on 2100, it looks like the second PR got accepted, and passed, and this is deployed in both 5.3.1 and 5.3.2. Let me know if you still have questions!

Hi @IamSigmund – the second PR was never accepted, and unless the fix was deployed within the last couple of weeks, it wasn’t in either 5.3.1 or 5.3.2 when we checked before Into the Box as we have a custom build process that currently merges that fix in, and when we removed that step, it broke again.

@IamSigmund cross posting here from LDEV-2100:

This remains marked as fixed in the 5.3.2 release. It is not fixed. The PR we submitted was never merged and LDEV-2115 is likely also not fixed. We asked on the mailing list (Announcing Lucee 5.3.2-RC ( and said the same thing there.

Please either accept the PR that resolves these tickets or remove the tickets from the list of fixed issues for 5.2 and 5.3. I get that legacy support for this tag is not a big issue for anyone but this has been marked fixed for months now and we have brought it to your attention on several occasions.

Hi @Samuel_W_Knowlton. As I mentioned in the CFML Slack, we’re still investigating. For the record, this didn’t make an agenda in a dev team meeting until May 13, so we’ve only really been looking at it for a couple of weeks. The reason it’s taking some time is because we were already in the midst of both the May sprint and the 5.3.2 final release. Thanks for your patience. @micstriit @isapir @cfmitrah.


Updating here, too, @Samuel_W_Knowlton. Please check the ticket again for another update. Should be fixed now.