Update 2

2018-12-03

A new update for Dynatrace AppMon 7-2-2 has been released! This update contains critical fixes and improvements. Using a controlled installation , you can select which agents when to update, without migration! The installation of updates containing critical fixes can prevent monitored application impact or monitoring data loss and therefore is strongly recommended for all users. Download here!

Resolved Issues

This update contains all changes of public updates of previous versions released to this date.

7.2.2.1030 Resolved Issues

Most critical issues since the last public updates

All resolved issues

Client

  • JLT-226772 - Fixed Performance and Memory issues for the Database Statements dashlet
  • JLT-226130 - Client Java updates will be installed into client/updates directory
  • JLT-224785 - System Profile can become corrupted (lost sensors, ...) due to client-server communication problems.
  • JLT-226329 - Client crashes when viewing host tile view with about 10000 hosts
  • JLT-226802 - Fixed issue where Client timezone selection would not apply
  • JLT-225702 - Prevents an ArrayIndexOutOfBoundsException in case an empty entry is selected in the Pattern drop-down menu within the Hostgroup configuration dialog.
  • JLT-227007 - "Show all nodes" now shows agent methods in the PurPath Tree.
  • JLT-225495 - Add missing download link to Java update dialog message.
  • JLT-228009 - Rate measures cannot trigger an incident. Therefore rate measures cannot be selected for incident rules any more.
  • JLT-228006 - If the number of result measures of a business transactions changes from 1 to n or from n to 1, historical data of the existing measure will be lost. In such a situation a warning will be shown to make the user aware of it.

Correlation and Analysis

  • JLT-226493 - Fix incorrect number of affected purepaths in errors dashlet when coming from drilldown
  • JLT-226327 - Use hashmap for incomplete subpaths per default
  • JLT-227612 - JLT-227612: Fix problem that only the first processing PurePath was shown in the PurePath Dashlet
  • JLT-226081 - JLT-226081: fix potential exception during session reanalysis
  • JLT-227602 - Always and immediately break first link in a circular sub-path reference to prevent problems resulting from temporarily existing circular references.
  • JLT-227320 - Adapt info node text, if PurePath was truncated by agent.
  • JLT-227598 - JLT-227598: Fix a problem with potentially duplicate keys in messaging analyzer
  • JLT-226895 - Improve correlation engine robustness by more gracefully handling sub-paths that stay in correlation engine even though they have been completed.

Server

  • JLT-225726 - An AssertionError may be thrown because of a round-off error
  • JLT-228236 - Always sync jre with highest version number from Server to Client
  • JLT-225607 - Portable client download will fail if the download request does not contain user-agent information.
  • JLT-227106 - SSO: Compressed SAML authentication (login) responses can't be handled
  • JLT-224349 - Collector fails to reconnect to the Server after an update rollback
  • JLT-227454 - ClassCastException in BaseIncidentFormatter.getViolations() prevents sending of incident notification mail
  • JLT-217336 - PurePaths that are separated from UserActions by the cross system profile split debug option can still push their application to the UserAction. This can lead to UserActions with an Application from a different system profile.
  • JLT-226325 - Adapt classloading for Java 11
  • JLT-225310 - Fixed the ordering of the shutdown sequence so that audit logging would be included before the JVM shuts down
  • JLT-226399 - The wrong Java binary may be set in the .ini file causing a startup failure of the AppMon component
  • JLT-228297 - Explicitly set the agent platform for each agent group to avoid accidental platform switches
  • JLT-208494 - Improved exception handling for the case an InvalidRegistryObjectException is thrown
  • JLT-227328 - Fixed an NPE that happens when a server with an enabled in-memory collector gets shutdown
  • JLT-225700 - NPE when reporting the System Information dashlet via REST call.
  • JLT-222314 - Updates can now define a version beyond which they cannot be rolled back.
  • JLT-219098 - Prevent potential NPE in AgentModelResponseSerializer31
  • JLT-227591 - Prepared the AppMon components (Server, Collector, Client) for future Java11 support
  • JLT-226429 - An invalid audit.config.xml file may lead to a server startup failure
  • JLT-226383 - Charting dynamic custom host measures without cache shows no data.
  • JLT-222508 - Still used agent resources may be deleted erroneously
  • JLT-227115 - SSO: used wrong hostname for sso/login/redirect and sso/logout/redirect URLs
  • JLT-221811 - Disable agent splitting for unused selfmonitoring measures
  • JLT-228000 - The sandbox (external process) for determining VMWare metrics will not be started if not supported by OS.

Tests

  • JLT-227143 - FqdnResolverTest fails frequently

UEM

  • JLT-225082 - Updated UemDatabase to version 1.0.21
  • JLT-226463 - Report URL is duplicated if a custom report url is configured.

Session Storage

  • JLT-220715 - JLT-220715: fix a potential session session-reading problem caused by concurrent close during shutdown
  • JLT-226555 - JLT-226555: fix a potential exception during session-read if a visit-session is already scheduled for deletion
  • JLT-227988 - JLT-227988: Handle an already deleted session more gracefully

Server Platform

  • JLT-226486 - Incident begin actions are triggered on incident update via REST if debug flag for plugin actions for custom incidents is enabled.

Documentation

  • JLT-226168 - Add support for JRE binary deletion

7.2.1.1008 Resolved Issues

Most critical issues since the last public updates

All resolved issues

Correlation and Analysis

  • JLT-225959 - Prevention and visibility of circular sub-path references during processing PurePath collection.
  • JLT-225975 - Add the transactionID to the tag used for linking subpaths. This is disabled by default.
  • JLT-226189 - Augments AppMon agent connection pool attachment information with occupied pool size.
  • JLT-225762 - Add a hard timeout for subpaths that, when exceeded, even break the path structure to make subpaths complete
  • JLT-225447 - Add AppMon agent protocol update support for mobile tags.
  • JLT-226713 - Improve event protocol logging by logging node attachments from events when they are still present.
  • JLT-226033 - In case a subpath timed out and a linked childpath was from an agent that disconnected in the meantime, the childpath wasn't force completed and therefore had to run in it's own timeout which made the whole transaction complete very late.
  • JLT-226010 - Update the latest event timestamp of a path only in case the event was successfully correlated to the path.

Server Platform

  • JLT-226497 - Concurrent calls to user management REST endpoints fail due to unintended side-effects on shared data.
  • JLT-223905 - Improved logging for failed log file uploads from AppMon agents.

Server

  • JLT-226892 - Make Apache request types (internal redirect, subrequest) available in PurePath dashlet
  • JLT-226676 - Show processing PurePaths can cause full gcs when the server is under high load. This can even lead to server restarts by the watchdog on very large heaps (XLarge256)
  • JLT-225845 - In rare cases when a system profile is removed, a NullPointerException is thrown. Be nullsafe when accessing PureLytics.
  • JLT-226681 - Prepared server memory management for future support of Java11
  • JLT-225723 - In rare cases non StatCounter objects cause Exception at startup, when monitoring correlation queue saturation. Just consider StatCounter objects.
  • JLT-225506 - Path expression is ignored in JMX probing request to AppMon agents, resulting in wrong agent response for complex attributes.
  • JLT-225504 - A stuck Collector connection may cause a forced Server restart
  • JLT-226032 - ArrayIndexOutOfBoundsException in ActionPurePathContext.finishNodes(..)

Java Agent

  • JLT-225289 - Servlet sensor throws NPE on JBoss EAP 6.4.x spamming the agent log file

Communication

  • JLT-225397 - Wrong HTTP header set for preemptive proxy authentication, which leads to communication problems when using HTTP tunnel via proxy with required basic authentication due to performance impact of challenge-response authentication
  • JLT-225837 - Security issue which allows to read files from the server system (with an unprivileged user)
  • JLT-225833 - Security issue which allows to read files from the server system (with an unprivileged user)

Client

  • JLT-224782 - Provide consistent user feedback when dashlet filters are used and and only percentage of data is available.
  • JLT-225853 - Agent picker used in Class Browser does not distinguish between different agents within the same process, which can lead to a different agent selection than intended by the user
  • JLT-223545 - For the client's REST interface a custom JKS can now be specified via system properties.
  • JLT-225523 - Default agent platform setting for new agent groups is not considered
  • JLT-225253 - Custom time frame filter is reset after drilldown.

Integration and Services

  • JLT-226075 - [Dynatrace Integration] When exporting the same measure to dynatrace from two different system profiles, only one metric would be created on dynatrace side.