Upgrading Lucee via a reinstall

[mdichi]

I know you can update Lucee from within the admin panel. That process is documented.

Instead of that, can Lucee be upgraded by uninstalling the current version and reinstalling a newer version?

I’ve encountered 500 errors after doing this in the past. To work around that we basically wipe out the entire webroot and reinstall our application. Then Lucee creates a new WEB-INF. I assume Lucee updates the entire WEB-INF with its own components from the new version.

Is there any easier way to do this so we don’t have to wipe out the entire webroot?

Thanks,
Mike

[andreas]

This is how I usually upgrade Lucee:

Error 'The REST Servlet is not configured in your environment' after upgrading to 5.3.10.120

In that case, that’s how I would reset the lucee server. This will wipe any setting configured through the Lucee Admin (web/server), also schedules and the admin password. But as you said, you didn’t setup anything in the Lucee admin, I’d reset your Lucee to the latest update as follows… backup everything so you can easily switch back if something goes totally wrong. Download the latest stable Lucee.jar from https://download.lucee.org Stop the Tomcat/Lucee service in the Windows Service Manag…

[mdichi]

Thanks.

That’s a lot of work. I think I’ll just uninstall Lucee. Wipeout the webroot (or rename it), reinstall an updated lucee, and then reinstall the entire app from scratch.

Fewer things can go wrong this way. It is basically a new application install.

Mike

[andreas]

This is up to you. Upgrading Lucee is as simple as just stopping Tomcat, replacing the lucee.jar with a newer file and restarting Tomcat. However, if you can and want to install from scratch, its always better to bump everythingy including Tomcat to a higher stable version.

[mdichi]

Just to follow up with this. Maybe it will help others.

We tried reinstalling 5.4.3.2 which has a Tomcat with the AJP vulnerability fixed. The application won’t startup. It won’t create a WEB-INF.

We tried install the latest (5.4.6.9). We get, “Tomcat Mod_CFML error mod_cfml request authentication failed!”. Investigating this leads to the type of fix that I was hoping to avoid. I don’t want to fiddle with IIS, AJP, connector settings. I just need an IIS + Lucee that work out of the box.

For now, we are telling customers that want a resolution to the AJP connector vulnerability that there isn’t one. We’ll have to find a combo of IIS + Lucee that are compatible.