I am updating Lucee 4.5.5.006 final to lucee-5.2.5.20.jar , windows server 2012, Tomcat 8, Java 1.8.0_144
I am a bit confused about where to put the jar file to update.
The update document says:
Add the lucee-5.x.x.xxx.jar you downloaded to the “lib” directory in your existing Lucee install.
But I have either:
E:\Lucee\jars
Which is full of jars, including a lucee.jar (modified 05/02/2015)
No, lib folder in here
Or
E:\Lucee\lucee-server\context\lib
Which has no files in. This context folder also contains the lucee-server.xml
Or
E:\tomcat\lib
Which has lots of jars but contains all the tomcat stuff so seems unlikely it goes here.
Is it E:\Lucee\lucee-server\context\lib it needs to go in, or somewhere else?
It looks like you’ve got some kind of non-standard set up there. How was it installed originally?
I don’t recall seeing a jars folder in any of my previous Railo or Lucee installations. Also where is Tomcat installed? Can’t see it in your screenshot.
My advice would be to do a fresh install if that’s possible. There’s a windows installer which makes sure everything is in the right place.
I’ve inherited it, so I don’t know the exact method, but it was Railo, upgraded to Lucee, then has been getting automatic updates of minor installations.
Both Tomcat and Java are in seperate folder structures, presumably to make them easier to update, and that has been the case. The screen shot is just the “Lucee” install
WebApps are all on a seperate drive
I understand that a fresh install may be optimum, but It’s a production system containing several different sites, so i’m not keen to reinstall, especially as I can’t replicate the system locally.
Are there any paths \ files that should be relative to the Lucee\lib directory that I can either search for or reveal programatically that would help define where I should put the update in my scenario? Or is there anything in the admin that can help define this?
The version file contains the code: 4.5.5.006-final-1485509741000
Which matches the version listed in my administrator, and was updated shortly after the release date of that patch on the 03/02/2017
There is an empty /lib folder in the same location as the version file:
E:\Lucee\lucee-server\context\lib
I also have an E:\Lucee\lucee-server\patches\ folder
Which has .ico files for all the 4.5 patches
But this has no \lib siblings or children
“4. Remove all other JARs in the same directory, however do not remove the directory “lucee-server” (or “railo-server”) if that directory is present, this is the case with default installations. Please note you must remove the JARs, DO NOT simply rename them.”
Can anyone give an example of names of any jar files that might be in the folder, so I can narrow down where it might be?
Looking at the jars in an old Lucee 4.5.5.006 war file, here’s a list of what I see. Your jars may not match this exactly, but it should give you an idea.
You might also think about hiring someone who can help you figure out your upgrade. There’s a million ways Lucee can be installed just due to the nature of how flexible servlet containers are so it’s difficult for anyone to really provide much help here without just seeing what’s on your file system.
I also know you don’t want to hear this, but the current situation you have with a server of which you have no knowledge, no control, and are terrified to replace it is a bad thing. Setting up a new instance of a server should not be scary, hard, or even time consuming and if it is, you’re either not equipped to do your job or not using the right tools. I literally have hundreds of servers on my local machine I spin up and down on a daily basis using CommandBox. The days of the giant server install that everyone is scared to touch are gone. Even if you are able to get this upgrade complete, I’d still recommend getting a fresh install just because you’re likely on a very old version of Tomcat if this is from the Railo days. You can use a tool like CFConfig CLI to export all your settings from the old server and re-import them into a new server which you can spin up on a separate VM to test.
