Impacts of upgrade to Java 17

Adeptia Connect version 3.7.2 comes with an upgraded Amazon Corretto JRE. The bundled Amazon Corretto JRE in this version of Adeptia Connect has been upgraded from v8 to v17 to ensure improved security.

This section discusses the impacts of this upgrade and the actions you must take to deal with them.

1. The upgrade to Java 17 may require you to handle the conflicts that may occur with custom jars or custom classes. You may come across the following scenarios wherein you need to take the necessary actions to address the conflicts. 

   1. Java packages used in the custom plugins, custom jars, or custom classes may have changed. To address this issue, you need to change the custom plugins, custom jars, and custom classes accordingly.

   2. Classes used in custom plugins, custom jars, or custom classes may have been deprecated or their implementation may have changed. To address this issue, you need to change the custom plugins, custom jars, and custom classes accordingly.

   3. Although Java 17 is backward compatible – code compiled with Java 8 continues to run on Java 17 most of the time – there are certain restrictions implemented in Java 17, for example, Java 17 restricts the use of certain packages and reflections. However, you can override these restrictions by adding the required entries in the launcher.properties file.

   4. External jar(s) in the ext folder may not be compatible with the upgraded versions of the framework. In this case, jars need to be upgraded accordingly.

2. With an upgrade to JRE v17,

   1. The SAML implementation in Adeptia Connect has got configuration changes. To learn more about SAML in Adeptia Connect, refer to this document.

   2. The JMS provider that connects to Apache Active MQ JMS server uses the two jars activemq-core-5.7.0.jar and geronimo-j2ee-management_1.1_spec-1.0.1.jar.  Ensure that:

      • You use these two jars when you create a JMS provider that connects to Apache Active MQ JMS server.

      • You have updated any existing JMS provider that connects to Apache Active MQ JMS server to use these two jars.
        For more details, refer to this page.

   3. The applets won’t open on the client machine. To fix this issue, perform the following actions on the client machine:

      1. Upgrade the JRE to v17.

      2. Download the IcedTea-Web tool zip.

      3. Extract the downloaded zip.

      4. Go to the path where you have extracted the zip.
         The folder structure would look like the following:
         <Drive>:\<Parent Folder (if any)>\icedtea-web-1.8.8.win.bin\icedtea-web-image\bin (This may vary based on where you have extracted the zip)

         Open

         

      5. Double-click itweb-settings.

      6. On the IcedTea-Web Control Panel screen, select JVM Settings.

      7. Point Java 17 in OpenJDK.

      8. Click Apply, and then click OK.

      9. Open itw modulejdk in a Notepad file, paste the following argument, and save the file.
         --add-opens java.base/com.sun.crypto.provider=ALL-UNNAMED
         
         

         Open

         

      10. Download the data mapper jnlp file that you want open in the applet.

      11. Right-click the jnlp file, and then click Open with > Choose another app.

      12. On the How do you want to open this file? pop-up screen, do the followings:

          • Select the Always use this app to open .jnlp files checkbox.

          • Click More apps.

          • Click Look for another app on this PC.

      13. Browse to the following path.

          …\icedtea-web-1.8.8.win.bin\icedtea-web-image\bin (This path may vary based on where you have extracted the IcedTea-Web tool zip).

      14. Select the file javaws.exe and click Open.