"There are no bugs if you don’t write any code."

This document details some of the known minor issues customers may experience when using Avantra with Java 17. 

Please keep referencing this page for changes and we'll update as we test ourselves with different scenarios and as we get customer feedback. We encourage customers to review this document in detail before deciding to roll out Java 17.

For information on installation and upgrade of Avantra 23.3 Agents with Java 17 please see our video here - https://www.youtube.com/watch?v=K9XT44CQm5g

Overview of known issues

Switching major Java versions resets JVM options

If an Avantra 23.3 agent is switched to use Java 17 using the automatic agent upgrade process, the JVM options are reset to the defaults for the new major Java version. Any customer changes to these options are lost. A backup is created before the major version change (Linux only).

Because Java 17 needs new/different options than Java 8, it is not possible at this time to combine the options. Any customer changes to these (for example memory limit changes) would need to be reimplemented.

XAN-4502 - Manual execution of the Windows Agent installer executable can set the wrong JVM properties with Java 17

When manually executing the EXE to upgrade an existing Windows based Agent, the JVM options are not correctly set according to the selected Java version.

We recommend using the built in agent update process from the Avantra UI to upgrade agents, including Windows based agents. You only need to upload the .bin installer file to the Avantra UI and can centrally manage the upgrade process.

For those customers that need to use the EXE upgrade method. This issue will be solved in a future release, or customers can manually edit the JVM properties to the correct value.