Forrester Total Economic Impact™ study finds Edwin AI delivered a 313% ROI for composite organization.

Read more

Partners

Docs

LM Academy

LM Community

Pricing

Platform
Solution
Industry
Role
There is no result.
Try it free

14-day access to the full LogicMonitor platform

Forrester Total Economic Impact™ study finds Edwin AI delivered a 313% ROI for composite organization.

Read more

Release Note

GD Collector 39.005

Feature Highlights

  • Collector Runtime Configuration Updates
  • Amazon JAVA Corretto Version Upgrade
  • Oracle JDBC Monitoring Timezone Improvements

Important: LogicMonitor will designate GD Collector 39.005 as an MGD release by the beginning of September 2026. All Collectors will be automatically upgraded to this version during the first week of October 2026.
LogicMonitor recommends that you proactively upgrade your Collectors to MGD Collector 39.005 before the automatic upgrade.

LogicMonitor GD Collector 39.005 is released on July 16, 2026. It is based on GD Collector 39.004 and includes the following additional updates:

Enhancement

Collector Runtime Configuration Updates

To improve compatibility with JDK 21, LogicMonitor now adds the required JVM module options to the Collector runtime configuration. This enhancement ensures proper operation of YAJSW, JMXMP, and BigQueue, reduces Java module access conflicts, and prevents excessive mapped-memory retention within the Collector JVM.

Enhancement

Amazon JAVA Corretto Version Upgrade

For security updates and improvements, LogicMonitor Collector now supports the latest Amazon JAVA Corretto version 21.0.11.10.1 for Windows and Linux Collectors. It is an upgrade from version 21.0.10.7.1.

Enhancement

Oracle JDBC Monitoring Timezone Improvements

To improve Oracle JDBC compatibility, LogicMonitor now enables timezoneAsRegion=false by default. This change helps prevent Oracle timezone-related connection errors in specific Oracle environments while maintaining compatibility with existing Oracle and non-Oracle monitoring.

Enhancement

Multiple Version Upgrades

LogicMonitor Collector upgrades the following components to apply minor security updates:

Component or Library NameCurrent VersionUpgraded Version
org.apache.commons:commons-lang33.12.03.18.0
io.netty:netty-all4.1.132.Final4.1.133.Final
org.apache.commons:commons-configuration22.12.02.15.0
lz4-java1.5.01.10.1
Apache Log4j Core2.25.32.25.4
Bouncy Castle BC-JAVA1.791.84
kafka-clients4.0.04.2.0
org.postgresql:postgresql42.7.242.7.11
jetty-serverjetty-utiljetty-httpjetty-io12.0.1912.1.7
Resolved Issue

Fixed the incorrect case of the Groovy InvokeDynamic flag from -DGROOVY.TARGET.INDY to -Dgroovy.target.indy in Collector configurations. For versions from GD Collector 39.004 through EA Collector 40.200, the system automatically runs a Healthcheck script to update the InvokeDynamic flag to -Dgroovy.target.indy in Collector configurations.

Resolved Issue

Fixed an issue that caused CIM DataSources to fail after upgrading Collectors from versions running Java 11 to EA Collector 38.100 or later, which run on Java 21. To fix the issue, LogicMonitor added the JVM option --add-opens java.base/sun.security.ssl=ALL-UNNAMED to wrapper.conf settings. For versions from EA Collector 38.100 through EA Collector 40.100, the system automatically runs a Healthcheck script to add the JVM option.