Upgrading to 8.0.1 failing when specifying custom application folder
Defect Fixed
When upgrading to 8.0.1 and using a renamed ROOT, you may be forced to manually specify the application folder, which will cause the following error:
The real error is logged within the 'YellowfinPatchLog' within the application folder:
Error encountered: java.lang.NullPointerException java.lang.NullPointerException at java.base/java.io.File.<init>(Unknown Source) at com.hof.patch.process.job.ExtractComponentLicencesJob.getRelativeTargetDir(ExtractComponentLicencesJob.java:37) at com.hof.patch.process.job.ExtractComponentLicencesJob.run(ExtractComponentLicencesJob.java:30) at com.hof.patch.PatchInstaller.runInstallJobs(PatchInstaller.java:467) at com.hof.patch.izpack.panels.YFPatchProcessPanel$YFProcessPanelWorker.run(YFPatchProcessPanel.java:299) at java.base/java.lang.Thread.run(Unknown Source)
This issue will ONLY occur if you have a custom ROOT folder and manually choosing the application folder.
For example, here is a standard Yellowfin install:
Here is one where the ROOT folder was renamed:
During the upgrade, if you were to manually choose the path c:\test\Yellowfin2\appserver\webbapps\MyApp, then the upgrade will fail with the the above error mentioned.
Note: In this case The Upgrade Patch log will be within the Backup you chose as part of the upgrade.
This is currently being addressed and will be released via a patch update. In the interim if you've run into this issue, please raise a ticket with the support team so we can organise an interim fix.
Regards,
David
This has been addressed in 8.0.2.
Comments have been locked on this page!