Failed Windows 3.4.3.0 upgrade

[Cantor, Scott]

On 1/15/19, 3:02 PM, "Dave Bartholomew" <Dave.Bartholomew at csueastbay.edu> wrote:

> I did a clean 3.4.3.0 install on a home laptop and did a file compare with
> the test IdP and found the Jetty files, system files, etc. to be
> identical. None of the many expected differences (conf, etc.) popped out
> as being problematic.

You have 3.4.1 stuck in the container and that's what it's running. The configuration is not part of the warfile so you have a 3.4.3 system config running against a 3.4.1 IdP warfile and jars. You're comparing apples and apples but running an orange.

The installer is nominally responsible for not allowing that to happen but this is Windows and its file locking makes it impossible to prevent this sort of thing from happening once in a while. It probably couldn't stop the running container cleanly and couldn't tell and it got stuck.
 
> Am I free to copy over any updated conf files (or other "user" files) that
> I haven't modified without being concerning about any dependencies?

I don't know what you're asking, but the non-system config files that were working before will run with either 3.4.1 or 3.4.3 jars because of the compatibility we have to guarantee. The system/ files do not, and have to match the running jars. The fix is to correct the container's broken state; stop it, double check it's stopped, blow away any temp files it's using and any copies of the webapp tree it's got stashed somewhere, and start clean so it unpacks the 3.4.3 war that the upgrader built in the idp.home/war directory and runs from that.

Searching for jars with the 3.4.1 suffix in the names is probably a good place to start cleaning.

-- Scott