With this release, the oldest supported ActiveGate versions are:
How long are versions supported following rollout?
The domain used for internal communication by OneAgents and ActiveGates that send data to Dynatrace SaaS will be switched from *.live.ruxit.com
to *.live.dynatrace.com
beginning June 30, 2021.
This change will only affect Dynatrace SaaS customers, and only if you:
Starting with ActiveGate version 1.215, you can annotate Kubernetes services, and there are three new optional annotations with a special format for client authentication. See Prometheus metrics for details.
Chromium 89 is now the latest supported version for synthetic-enabled ActiveGates installed on Ubuntu 16.04, 18.04, 20.04, Red Hat, and CentOS 7 and 8, 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>
The .215 GA release contains 3 resolved issues.