Exception on lucee server panel after update

dev support
1

OS: Alma Linux 9.7
Java: OpenJDK Runtime Environment Temurin-21.0.9+10 (build 21.0.9+10-LTS)
Tomcat: 11.0.15
Lucee Version: 6.2.4.24

After updating from 5.x can’t open the lucee server panel anymore. When provided the correct password the following NullpointerException is thrown:

Cannot invoke “lucee.runtime.spooler.SpoolerEngine.getOpenTaskCount()” because the return value of “lucee.runtime.config.ConfigWebPro.getSpoolerEngine()” is null

When double check with another updazted instance I can see that here the whole “security” part in the .CFConfig.json is missing. But even when adding the security part it is still nut working. Any input on what the root cause could be and howto resolve this?

regards

Romeo

2

The recommended way to upgrade from Lucee 5.x to 6.2 is to install a fresh Lucee server.

Alternatively, you can upgrade the server using an .lco file:

  • Remove all files inside lucee-server/patches/ and lucee-server/felix-cache/.
  • Restart the server to initialize the existing (5.x) server.
  • Obtain the Lucee 6.2 .lco file and place it in lucee-server/deploy/.
  • Restart the server again to apply the .lco update.
3

Hi

Thanks for your response.
Just to assure. I assume that also the lucee-6.x.jar from the /lib needs to be removed in the first step (and assure that there is the lucee-5.x.jar in place) otherwise there will be no switchback to 5.x to trigger the update again. correct?

regards

Romeo

4

Yes, that’s correct. You need to remove the lucee-6.x.jar from /lib first and make sure lucee-5.x.jar is in place. Otherwise, the server won’t switch back to 5.x to trigger the update.

5

“reupgrade” did not resolve the issue. To make a long journey short. Digging further using the stacktrace and the java source code I could track down the issue to the getLog() call in the Config Object used by a RemoteClient Object. Then I saw in the .CFConfig.json of the web (not the server) the following:

“loggers”: {
…
“remoteclient”: {
“appenderArguments”: “path:logs/”,

I changed that to

"remoteclient": {
  "appenderArguments": "path:{lucee-web}/logs/remoteclient.log",

Matching the pattern used by other loggers. lucee restart → Bingo!

lucee6 is failing the hard way with a config which was running fine (at least did not throw a NullpointerException…) on lucee5

Happy the server panel it is finally working again.