Has anyone come across this?
It happened after upgrading from Lucee 5.2.7 to 5.4.7.3. We first tried this on our dev boxes and all is fine. At one customer site ThreadDeath occurs. One difference is that the customer is running on Windows 2016 while our dev boxes are 2019 and 2022.
The error occurs when application starts up in Application.cfc’s onApplicationStart. We have some code in there to do some app initialization. Nothing that is very CPU intensive.
try a fresh install?
5.2.7 is so old it can already legally drink and has 3 kids, it’s probably still java 8? (Jun 7, 2018) so 8u181 ? Tomcat has also heaps of CVEs since then too
I did 5 installs of 5.4.7.3 from scratch. When I do a Lucee update, I uninstall the old Lucee, delete the c:\lucee directory and reinstall the application from scratch.
On the 6th try I went back to Lucee 5.2 and it worked.
I’ve probably done at least a hundred installs of our app, which uses Lucee. The problem is each version of Lucee is a little flakey in terms of the install and startup. Some versions simply don’t work reliably. Version 5.2 has been solid for a long time.
With newer versions of Windows and CVEs we are been forced to update. So, I’m looking for a reliable version of Lucee.
In this particular case, I noticed if I remove the Application.cfc, I can run a simple CFM file. The app won’t run, because the initialization in Application.cfc didn’t occur. Then I tried commenting out parts of the Application.cfc. The problem is on the first CFQUERY. It gets stuck there and then times out with a Thread Death.
Mike
As you are going thru this upgrade process, i’d really recommend simply going to 6.2.1-RC, why battle tech debt? 5.4 LTS is EOL end of this year
As for the figuring out why you are getting a thread death, my approach would be the good old debugging it by going thru your Application.cfc startup workflow and adding some logging at various points using systemOutput("start cache"); to find out which section of code which ends triggering the threadDeath?
If you need professional assistance, DM me, I can solve this for you
You make good points but I’ve disappeared down the rabbit hole for days trying to get different versions of Lucee to work reliably for us.
In any case, I decided to skip mowing the lawn and try 6.2.1 on one of our dev boxes. It didn’t take long to encounter a problem.
I uninstalled 5.4.3.7. Wiped out the \lucee directory. Started with a fresh web root (created in IIS on Windows 2022 Server). I installed Lucee 6.2.1-RC.
I created a simple test.cfm file with has #Now() in it. It runs but no WEB-INF directory was created.
The rabbit hole deepens.
there is no WEB-INF anymore in single mode, only the lucee-server/context
you can switch via the admin back into multi mode
