![]() There’s always value in multiple notifications and perspectives.Īs you note (but we should draw out), this is ONLY about the installers. You’ll see I expressed the same surprise and concern (and desire to warn others) as you do here, when I experienced it the problem a week after the new JVM installer was released Jan 17. Michael, given your last question (“what do other people think about this…”), I offer my post about this from a few weeks ago:īeware that latest Oracle JDK installers will REMOVE older JDK installs of that version ![]() Thanks for reading my long-winded rant, and I look forward to hearing others’ thoughts. What do other people think about this change of behavior? Have you managed to find a workaround to allow two or more versions to be installed side-by-side? Unfortunately, the link to bug JDK-8292822 is password-protected, and I do not have access to this site, so am unable to read why this decision was made: ![]() If the JDK11.0.18 installer is launched when JDK11.0.19 is already installed, it will show an error that a newer version of this JDK family is already installed. There may be a Files In Use dialog shown if the older version was running and locking JDK files. If the JDK11.0.19 installer is launched when JDK11.0.18 is already installed, it will auto-upgrade them to JDK11.0.19. Thus the 11.0.18 and 11.0.19 releases will both install into %Program Files%\Java\jdk-11 by default, and they both cannot be installed at the same time. all updates of the same release must share one installation directory. Windows JDK installers must install the Oracle JDK in %Program Files%\Java\jdk-%FEATURE% instead of %Program Files%\Java\jdk-%VNUM%. I tracked down this change of behavior to the release notes for JDK 11.0.18:ĭisable Side-by-Side Installations of Multiple JDK Updates in Windows JDK Installers (JDK-8292822) This new installation behavior seems to me to be incredibly problematic for server administrators who want to prepare the new JDK in advance, switch to it, then have the old version ready to fall back to if something goes wrong when running CF with the new version. This time around, however, when I ran the JDK installer, and manually changed the installation path to C:\Java\jdk-11.0.18, it proceeded to remove the 11.0.12 and 11.0.14 versions, and install 11.0.18 in the 11.0.16 directory, reporting that some processes were already using the JDK (not surprising, CF and add-on services were still running). I’m sure most of you have done the same thing on many occasions. I have then updated the path to the JVM in the CF Administrator, and manually updated a couple of config files in the CF instance directory tree. ![]() When updating the JVM previously, I have installed the new JDK (Oracle, downloaded from the Adobe site) to sit alongside the existing JDKs already installed: C:\Java\jdk-11.0.12 Although not directly related to ColdFusion per se, I just came across what could be considered a serious issue when preparing to update the underlying JVM used for CF 2021 from 11.0.16 to 11.0.18. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |