Guys I really need help with these couple issues we are seeing since changing from Lucee 6.0.3.1 to 6.2.1.122.
Just for context: as part of upgrading to 6.2.1.122 I upgraded Java from 11 to 21 and Tomcat from 9 to 11. Everything worked fine on dev but when applied to our prod servers, under production load Lucee would see what appears to be random issues:
Lucee starts OK but then falls over within the next hour. No errors posted to catalina.out, just normal entries. It just starts throwing 500 errors on each site.
Lucee starts partially OK. Say roughly 100 sites will load fine but then another 100 will throw 500 errors. Again, no errors written to catalina.out.
To try fix this I opted for a clean install i.e. uninstalled lucee, deleted /opt/tomcat then reinstalled Lucee keeping the supplied Java and Tomcat.
Sadly that didnāt help and we are still seeing the exact same stability issues. Again, catalina.out is clean, only normal entries. No errors posted when the 500 errors start.
One other thing we are seeing that appears odd is really high cpu bursts lasting 30 minutes on average, on the hour, every hour, for roughly 48 hours. When looking at the threads, it is the Lucee Controller thread. Once it settles after 48hrs the server falls over shortly after and we have to restart it again.
Sometimes we have to restart lucee 2 or 3 times within an hour until it comes up properly and stays up.
Before this upgrade/clean install, our prod servers were perfectly stable.
The only thing I havenāt tried is deleting the .CFConfig.json file and manually enter all the settings again. No idea if this will help or not.
@Zackster Nothing for sure, just a shot into the dark to try to isolate and rule out stuff, but sincerely I donāt have any further insights into Lucee anymore (unfortunately I havenāt been as involved as I wanted to be with the Lucee development lately)
This only occurs when your server has been running more than 30 days
I believe you can try stopping the server, purging your dynclasses folder (lucee-server\context\dynclasses) to get 30 days without problem, also per /WEB-INF/content/dynclasses, you are running in multi context mode Iām assuming?
How many sites are you running under that single install?
Out of interest, how many files are under that folder??
@Pondrey I very much appreciate your update because this was the main issue I was waiting for to be resolved before upgrading to 6.2 in my own production server.
