After updating to 6.1.1.118 Lucee server goes down at least 1 time a day and I have to restart it.
I downgraded to 6.1.0.243 and no problems for over 2 weeks. I upgraded again to 6.1.1.118 and after a day and a half it was Down again.
Has anyone else had stability issues with 6.1.1.118?
Michele, I gather that your primary goal here is simply to find if others might know of an instability issue in that specific Lucee version, is that right?
And if no one confirms it, are you then interested in diagnosing the problem? Or will you just camp at the older one and wait to see if things get sorted out?
Itâs a sincere question, without judgment.
Iâm just saying thereâs much more we could ask and that you could offer, to better understand and perhaps resolve why your âserver goes downâ. Thereâs often far more specific aspects to that, which could identify the specific problem.
It might even serve to help the support folks address an issue in Lucee or a related library. But for you we might at least identify a possible workaroundâŚand one that would allow you to update and continue to update Lucee until some Lucee issue is resolved.
But I realize some wonât want to âbotherâ with that sort of effort, or may feel itâs not their job, or again are simply ok to park at an older version and wait. Iâm just trying to tease out where things stand for you, as well as to guide us in next steps if no known instability issue for that version is identified.
@carehart is by far the expert, on all things ColdFusion servers â period.
If its a paid production site, it maybe well worth having him poke around your setup, as his one hour of suggestions is literally better than a dozen hours by senior engineers all of whom deal with tomcat, ColdFusion and other application servers.
Having only one server thatâs always in production, not a good idea long term. I suggest you snap shot it / clone it, do what ever you must to have a working secondary replica of it. Then build a non-production server for testing and or familiarize yourself with redundancy.
Terry, thanks for the kind (if overstated) regards.
Michele, the goal of my question was to find simply if you DID want to dig into diagnosing things. Now that youâve confirmed you do, I and others can offer more thoughts. I didnât then, for the reasons stated.
And now you add âthis is productionâ, and âcanât do experimentsâ. Sounds like youâve been burned before. Diagnostics need not entail impact on prod.
So first, please clarify what âserver goes downâ has meant in this case? Lucee stopped responding? Even the admin? And I presume you looked for but found ânothing in the logsâ at the time?
And is it that you have nothing in the form of any monitoring of Lucee? No fr, no seefusion, no apm, no jdk tools? And by âno experimentsâ, does that mean you wonât consider enabling them, even to possibly diagnose and resolve this problem (and other future ones).
Again, you may just want the solution, and someone else may soon gather enough from whatâs been said so far to offer one. Iâm asking more questions to draw out what you do and donât know, and what we may or may not be able to obtain through this dialogue.
Yeah, Iâd be curious what the last operation is before the crashes. Is it something weird like PDF creation? Accessing a drive path that doesnât exist? Just making stuff up, but meant to illustrate that thereâs âregular website / CF stuffâ and thereâs more complex features that may have a problem on the specific hardware, OS, etc.
SAME issue here. Server has been running fine for over a year. Then saw an update in the Admin last week so I updated, and now server goes DOWN every couple of days. Rolling back to 6.1.0.243.
Same here as well, and same with 6.2, as far up as 6.2.0.298-RC. Itâs always java heap space for us in catalina.out, but havenât figured out why yet. Downgrading also worked as a bandaid though weâre trying to narrow down further on a staging server without luck yet.
Same here. Every build of 6.x has caused similar issues for us. Narrowed it down to using threads and database connections in them and/or scheduled tasks using threads.
Same problems here - our case is perhaps a bit more esoteric, as weâre doing object serialization at the Java level, but the bottom line for us is that 6.1.1.118 is completely unusable for our purposes.
Our specific reason is that the work-arounds we built with Lucee 5.x for LDEV-2138 donât work, and our attempts to come up with a new work-around are stymied by a class loader problem (6.1.118 says âno such method existsâ for a method we can call successfully with 6.1.0.243). We still have to probe around and find what weâre looking for, but we canât even start if we canât get Lucee to call our Java methods
We still have to probe around and find a new work-around for LDEV-2138, but at least with 6.1.0.243 we can reliably call our Java methods.
=====
Java 11 update 25
Lucee 6.x running on Alma Linux 9 (Intel)
There is nothing overly complex on in my code, itâs quite basic. I was a little concerning to see these threads as I am on 6.1.1.118 , however I can confirm that I have had no problems at all.
I canât remember when I upgraded but itâs been a while so likely shortly after it was released which I believe was November.
On 6.2 the problem seems to be solved.
I updated to 6.2 already 10 days ago and since then the server has not crashed.
Instead every time I tried to update to 6.1.1.118 after about 1 day it was down. In the logs I only found a timeout without specific indications.