With this release, the oldest supported ActiveGate versions are:
How long are versions supported following rollout?
When you run the update to ActiveGate 1.213, the contents of the instance.properties
and multitenant.properties
files are migrated to a new authorization.properties
file. The instance.properties
and multitenant.properties
files remain as backup, but any settings applied in them won't take effect.
The change results in a new format for setting up ActiveGate for multi-environment support and Tenant token rotation, which are now both performed in the authorization.properties
file.
The authorization.properties
file is stored in the ActiveGate configuration directory.
The configuration parameter ignoreClusterRuntimeInfo
in the [connectivity]
section, can now be specified during ActiveGate installation for Linux or Windows, to facilitate immediate connection to a reverse proxy or a load balancer.
Chromium 88 is now the latest supported version for synthetic-enabled ActiveGates installed on Ubuntu 20.04, Red Hat, and CentOS and bundled with the Windows ActiveGate installer. For more information, see Requirements for private synthetic locations.
This affects ActiveGates for which continuous update began before version 1.165.
If your launcheruserconfig.conf
file contains the following parameters:
-memorylimit.percentage=80
for ActiveGates versions earlier than 1.205-java.xmx.relative_part=80
for ActiveGate version 1.205+your ActiveGate will not automatically start after the update to version 1.213 and your DynatracegatewayLauncher_<timestamp>.log
file will contain the following log events:
2021-05-19 17:21:25.011 UTC [273cc8f5] severe java: [child stderr]: OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be removed in a future release.2021-05-19 17:21:25.011 UTC [273cc8f5] severe java: [child stderr]: Unrecognized option: -java.xmx.relative_part=802021-05-19 17:21:25.011 UTC [273cc8f5] severe java: [child stderr]: Error: Could not create the Java Virtual Machine.2021-05-19 17:21:25.011 UTC [273cc8f5] severe java: [child stderr]: Error: A fatal exception has occurred. Program will exit.
This typically occurs if you have customized the launcheruserconfig.conf
file and the automatically added parameter is appended to the end of the parameter block.
ActiveGate versions earlier than 1.205
ActiveGate version 1.205+
-vmargs-Dhttps.proxyHost=<host>-Dhttps.proxyPort=<port>-Dhttps.proxyUser=<user>-Dhttps.proxyPassword=<password>-memorylimit.percentage=80
-arguments_section.jvm-Dhttps.proxyHost=<host>-Dhttps.proxyPort=<port>-Dhttps.proxyUser=<user>-Dhttps.proxyPassword=<password>-java.xmx.relative_part=80
Use the workaround to clear the problem.
launcheruserconfig.conf
file.-memorylimit.percentage=80
for ActiveGate versions earlier than 1.205-java.xmx.relative_part=80
for ActiveGate version 1.205+launcheruserconfig.conf
file.For example:
ActiveGate versions earlier than 1.205
ActiveGate version 1.205+
-memorylimit.percentage=80-vmargs-Dhttps.proxyHost=<host>-Dhttps.proxyPort=<port>-Dhttps.proxyUser=<user>-Dhttps.proxyPassword=<password>
-java.xmx.relative_part=80-arguments_section.jvm-Dhttps.proxyHost=<host>-Dhttps.proxyPort=<port>-Dhttps.proxyUser=<user>-Dhttps.proxyPassword=<password>
This release doesn't contain any user-facing resolved issues.