Due to a new version of log4j being released to completely fix the security issues found, log4j has been updated to 2.16.0. Further, Nearly every other library has also been updated to ensure that as of now, even the strictest scanners will validate the security of all the libraries used.
Added code to wipe central manager analytics if memory usage becomes too high automatically, as this is the most likely cause of any issue.
Added code to condense parameters in queries for logging to a few, avoiding issues where millions of parameters would result in queries not being logged due to their size.
Removed an extra debug line in the previous build that could cause excessive log entries, even when verbose debug mode was not enabled.
Added retry logic on auto-driver downloads to avoid issues if there is a transient error.
AWS Marketplace images - Added the RDS CA certificates to the image by default to allow drivers to validate the CA cert issuing the database cert.
Dramatically improved regression tests, although these didn’t result in any actual code changes.
Improved warnings if there are overlapping ports for DNS or HTTP monitoring.
You can now throttle certain warnings that could generate large numbers of messages.