cfml

Got an exception in Lucee admin when doing a restart...

*Lucee 5.4.4.38 Error (java.lang.ClassCastException)*
*Message*
class lucee.runtime.tag.Abort cannot be cast to class lucee.runtime.tag.Abort (lucee.runtime.tag.Abort is in unnamed module of loader org.apache.felix.framework.BundleWiringImpl$BundleClassLoader @7ce973b6; lucee.runtime.tag.Abort is in unnamed module of loader org.apache.felix.framework.BundleWiringImpl$BundleClassLoader @173373b4)
*Stacktrace*
The Error Occurred in
*/admin/restart.cfm: line 7*
*called from* /admin/web.cfm: line 570
*called from* /admin/server.cfm: line 2

It's nae bother to me, and it's not happened before. Just in case y'alls Lucee bods wanna know and look into it. [shrug]

It's a stock install of 5.4.4.38 from the official Docker image of same. Nginx variant.

Does restarting the instance resolve the issue?

No.

But I needed to completely rebuild then container anyhow, and issue is gone now.

By any chance was the reason you needed to rebuild the container due to permission issues?

It looks like the Felix OSGi loader was having issues, which might be a file permission issue. Just a guess on my part though, as I don't understand Felix well at this point.

Nah, it's just that I'm dev testing two different pieces of work that have different container configs ATM (env var differences). PAIN IN THE BUTT!! :smile:

Test one... feed back to the dev... switch to the other whilst they're reworking &amp; test the other piece... rinse &amp; repeat.

I've rebuilt these containers (there's 7 of them) about ten times today so far.

Adam -- you didn't try deploying the 6.x lex files when that happened, right?  I've run into several issues doing the in-place update to 6 within the official containers.

Nah it's the stock `lucee/lucee:5.4.4.38-nginx` image. We are prewarming a coupla extensions (don't get me started on this again... ;-)). There is no way I will be touching v6 for at least six months after release. Probably more like a year. But realistically we will never move to 6.x

TO BE CLEAR, I am not asking for help here, and I'm not trying to solve anything. The intent was just to let Lucee know there's a potential issue _they_ might want to look at. *I* don't care. It's not impacting me.

I realise I was vague here:
&gt;  Got an exception in Lucee admin when doing a restart...
By that I mean "clicking the [Restart Lucee] button on the Restart tab of Lucee's server admin UI".

It processes for some seconds, then spits that error out after about the same length of time it usually takes to restart and take me back to the login screen.

NB: the restart _doesn't actually happen_. So it's failing a wee ways into the process, but before it does whatever "restarting" is.