Update 15

2019-08-01

A new update for Dynatrace AppMon 7-2-15 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.15.1027 Resolved Issues

Most critical issues since the last public updates

All resolved issues

Server Platform

  • JLT-239103 - Serialization exception when requesting Support Archive data from Collector with older version if Support Archive was requested via REST
  • JLT-238775 - Server and Collector log files currently open for more than 1 day not included in Support Archive exported via REST if respective component is running on Windows operating system

Server

  • JLT-239068 - Allow to prevent memdump postprocessing in backend-server also for non production environments using a debug option. Memdumps will stay raw in case that option is set and no AnalysisServer is reachable.
  • JLT-238329 - Show shared license information for host based technologies (.net, IIS)
  • JLT-238705 - Make it possible to disable the evaluation of API measures via a debug flag
  • JLT-239152 - AssertionError may happen in SparseTimeSeries if assertions are enabled
  • JLT-239143 - Reduce lock contention in ApplicationDetectionState
  • JLT-238708 - Connection timeouts in collector-server communication due to lock contention during serialization and update of large system profile
  • JLT-239151 - Correct misleading log in DirWatchingAgentResProvider: "No exact match for resource bundle version ..."

Client

  • JLT-239019 - Make it possible to disable 'dynatrace.com' web request by the Client using a Server debug flag
  • JLT-238860 - Agent Version Pinning: "Use version of active update" does not work when automatic Agent updates are disabled
  • JLT-234707 - Update lz4-java library to version 1.6.0 in order to prevent "LZ4Exception: Malformed input"

Collector

  • JLT-239309 - Very large certificates prevent restart

7.2.14.1014 Resolved Issues

Most critical issues since the last public updates

zAgent

  • ONE-25823 - zLocalAgent cannot maintain a connection to zRemoteAgent after an initial connection failure.
    • Impact: zRemoteLocal connectivity problem.
    • Cause: When the zLocalAgent fails to connect to the zRemote on startup it will not be able to maintain subsequent connections because of missing pings.
    • Solution: Ensure the timer thread is not shutdown inappropriately to allow periodic pings.

All resolved issues

Correlation and Analysis

  • JLT-238478 - Transactions created from orphaned local paths are marked as lost&found.
  • JLT-238597 - Correct handling of local path transaction size estimation, circular reference detection, and discarding.
  • JLT-238473 - Avoid loosing the original corruption reason of a path in a special case.
  • JLT-238403 - Fix a problem during drill down from the Entry Screen to Web Requests

Dashboard

  • JLT-238914 - Cannot save memory dump comparison dashlet from a Windows client on a Linux server.

Client

  • JLT-232776 - Add info dialogs to inform users about peculiarities when using the agent platform selection and the version pinning features for Message Broker agents
  • JLT-237740 - Remove keynote support in synthetic integration configuration.
  • JLT-238660 - Potential NullPointerException when Entry Screen is opened before initialization of available dashlet filters is finished.
  • JLT-238778 - Cannot save dashboards anymore after saving a dashboard failed.

Server

  • JLT-234554 - Create a minified version of the current agent resource bundle to prevent cases where no UEM agent for an agent version can be found
  • JLT-238831 - Orphaned system profile permission mappings in user groups when system profile is deleted.
  • JLT-238659 - Logging of stack trace can be turned on for unknown config measure.
  • JLT-238624 - Dynamic measure cache will be cleared after renaming is finished
  • JLT-238650 - On frontend server log message regarding missing id for config measure throttled and stacktrace added.

Collector

  • JLT-238696 - Agent version and platform configuration for Host, Message Broker and zAgent may not be applied

zAgent

  • ONE-25823 - zLocalAgent cannot maintain a connection to zRemoteAgent after an initial connection failure.

7.2.13.1061 Resolved Issues

Most critical issues since the last public updates

All resolved issues

Server

  • JLT-238508 - ConcurrentModificationException when processes are fetched
  • JLT-237682 - Automatically take a CPU sampling of the Server backend process if an internal queue is unhealthy and make the sampling a part of the Support Archive
  • JLT-238483 - NullPointerException when the entry screen is loaded without time filter given
  • JLT-238470 - Measure names in server and client side reports are different
  • JLT-236836 - Server config cannot be stored because of a FileAlreadyExistsException
  • JLT-236584 - IdP certificate was not migrated properly when migrating from 7.0 with SSO configuration enabled
  • JLT-237517 - Fixed incorrect serialization of filter criterion.
  • JLT-236575 - Log spam: "[BaseDtJreCenter] No matching dtJre found for java version ..."
  • JLT-238429 - Very rarely, debug flag settings may not be applied correctly
  • JLT-238481 - Fix handling of empty CPU samplings
  • JLT-234295 - Support for Agents which identify by 64-bit ids
  • JLT-238411 - In rare cases when autodetected applications change an exception occurs.
  • JLT-236102 - Log information added

Plugins

  • JLT-238381 - SNMP Action Plugin V2 cannot be deployed using the client plugin development feature since it fails the test stage

.NET Agent

  • JLT-237686 - Fix a problem that happens when random Numbers are provided by the Oracle DB-Driver as DB-Pool-Usage
  • JLT-238104 - .NET AppMon agent was not loaded, when automatic agents updates were disabled and the agent version was locked to a specific version

Correlation and Analysis

  • JLT-238761 - Improved assertion messages for problem analysis.
  • JLT-237698 - Support UEM correlation of transactions that have the relevant information on a subpath

Client

  • JLT-238413 - NPE check added for SSO certificate validation in case server is not available.
  • JLT-236583 - After upgrade from 7.0 to 7.2 error message was displayed although SSO service provider certificate was configured correctly.
  • JLT-238484 - Fixed NPE in ToolbarControl

7.2.12.1046 Resolved Issues

Most critical issues since the last public updates

All resolved issues

Server

  • JLT-237414 - Improved debug logging for analysis of early discarded PurePaths
  • JLT-237410 - A CPU sampling will be created automatically if RTA queue runs full.
  • JLT-237461 - Fixed NullPointerException that might occur when using AppMon agents and a URI string cannot be resolved asynchronously.
  • JLT-237605 - Missing JVM config measure will be logged without stack trace.
  • JLT-236351 - Log information added.
  • JLT-237790 - Enabling MQ Series support using AppMon Agents platform.
  • JLT-235173 - Make AppMon agent version check future proof (add support for major versions greater than 1)
  • JLT-232207 - In case of SystemProfileIntegrityException additional information will be logged.
  • JLT-237874 - Logging of stack traces turned off on backend server in case of non bijective mapping exception.
  • JLT-237933 - Log information added for changing the collation of columns of dynamic measure table.
  • JLT-234703 - Allow automatic font migration for AdoptOpenJDK if system property is set

Communication

  • JLT-236592 - Changing a System Profile with many applications may impact Collector connectivity if it has a high number of Agents connected.

Client

  • JLT-235782 - Client may crash on some Linux distributions if AdoptOpenJDK is used
  • JLT-237512 - Drilldown from certain aggregated nodes in Transaction Flow doesn't work correctly.
  • JLT-232213 - Improve error handling in performance warehouse settings dialog
  • JLT-236530 - Connected agents column in Collector overview should not consider self-mon agents unless Client debug mode is enabled
  • JLT-237617 - Refactor transaction flow implementation for maintainability.
  • JLT-237638 - Do not throw "RuntimeException: Widget disposed too early" when Client is shut down
  • JLT-237553 - Transaction Flow: No detailed timing information in hover-popup of aggregated database nodes.
  • JLT-237877 - NPE during global downtime creation in the shutdown dialog when communication to server temporarily fails

Charting

  • JLT-237610 - Data of last entry in a dual axis chart is not fully shown for clustered bar charts

PWH

  • JLT-238038 - In case of ORA-14411 on truncating a temp table on cleanup it will throttled logged and the stack trace will be suppressed.

Correlation and Analysis

  • JLT-236367 - SubPathV2: Handle "dropped" LocalPaths in AppMon.
  • JLT-237916 - Fix potential link problem from local sub-paths to sub-paths.
  • JLT-236609 - Remove heavy logging in case a subpath cannot be linked due to invalid timestamps.

Server Platform

  • JLT-238060 - Wrong JVM detection for Java Agents running on Azul Zulu JVM leading to missing GC process metrics.

Installer and Build

  • JLT-237625 - AppMon Collector init.d script would fail if you set an instance name but no runasuser. Note: can only be fixed by using an up-to-date installer, can't be fixed with the normal update mechanism.

UEM

  • JLT-237578 - Updated one-agent-uemdatabases to version 1.1.0

Agent

  • JLT-237792 - Add support for Apache DBCP2 version > 2.4

Dashboard

  • JLT-237949 - Date columns are missing in XML report for some dashlets.

7.2.11.1059 Resolved Issues

Most critical issues since the last public updates

All resolved issues

Correlation and Analysis

  • JLT-233191 - Make AppmonAgent's paths truncated instead of corrupted in case they get truncated on the agent.
  • JLT-234288 - Speedup completion of deeply nested transactions.
  • JLT-237890 - Disable fix of JLT-234288 temporarily.
  • JLT-236875 - Mask client IP address on AppMon agent web request node attachments, if configured accordingly.
  • JLT-235888 - Merge AppMon agent exception nodes on server, behavior similar to Classic agents.
  • JLT-236573 - Fix a potential problem in php errordetection when the exception message is empty
  • JLT-226455 - Improved processing of Mobile ADK Version string to cater for changes to the format

WebUI

  • JLT-234442 - WebUI: Not all confidential strings for PP details view were masked

Server

  • JLT-236600 - A measure which was just added will not be logged to have no id in dynamic measure table.
  • JLT-225200 - Improve backendsampling by monitoring each correlation queue.
  • JLT-235890 - Transaction Flow loads slowly due to redundant queries for health information.
  • JLT-236127 - The debug flag to disallow private key deployment did not apply when the request was directly invoked.
  • JLT-235542 - Added debug flag to allow the frontend server to continuously attempt reconnect despite unusual reconnect termination.
  • JLT-231621 - Avoid agent connections before the first full collector sync is finished
  • JLT-231500 - Deadlock between AvailabilityCenter and InfrastructureConfigCenter during shutdown by signal
  • JLT-236851 - Improve logging when deleting session and the server process doesn't have access rights
  • JLT-236312 - Schedules with occurrence based end time specification are again executed after a server restart even if the number of configured occurrences has already been reached.
  • JLT-236608 - In case of nested external call tiers use innermost tier when debug flag (com.dynatrace.diagnostics.core.analytics.puremodel.tierdetection.useInnermostTier) is enabled.
  • JLT-232255 - Very rarely the server may hang on shutdown or restart
  • JLT-236877 - Cross system profile split option temporarily ignored for AppMon agent upon reconnect, which can result in broken PurePaths.
  • JLT-236654 - Fix a potential problem during memdump creation
  • JLT-235971 - Try a resend of heartbeat messages on the Collector to avoid a stalled global agent time when using AppMon agents
  • JLT-236430 - Settings for frontend server memory for xlarge256 and xlarge512 changed to 64GB / 128GB in native launcher.
  • JLT-236871 - Debug Log of License Checker unclear.

Client

  • JLT-235513 - NullPointerException when server connection is lost while editing a user.
  • JLT-236532 - Full stacktrace is logged when widget is already disposed in a deferred event handler.
  • JLT-236300 - Vertical bars are visible in Table details view's text fields.
  • JLT-236527 - System Information dashlet unresponsive after unchecking a System Profile.
  • JLT-235787 - Too eager disposing of resources in some UI components.
  • JLT-235966 - Falsely reported UEM exhausted incident for self-monitoring when all UEM volume is reserved.
  • JLT-235150 - Host health history is not shown in the infrastructure overview
  • JLT-234501 - NullPointerException when typing in Client Settings -> Time Zone combo.

PWH

  • JLT-236089 - System profiles will be synchronized with PWH in a sychronized manner to avoid race conditions.
  • JLT-236296 - Modifications of selfmonitoring system profile will be pushed to frontend server.
  • JLT-231446 - Splittings will be logged in hex if containing multi byte character and DB does not support UTF16.
  • JLT-236350 - Splittings which ends in "~" are handled special to avoid cache inconsistency.
  • JLT-235936 - Special handling for single byte characters > 0x80 in splittings implemented. This is to avoid cache inconsistencies in case the database does not support utf16.

Collector

  • JLT-236098 - Agent is rolled back to the classic agent platform if the agent is bootstrapping during a Server downtime even though the AppMon agent platform is configured for the agent
  • JLT-236440 - Fixed problem in collector memory managed that reacted too late which can lead to a non responding collector which can have negative side effects on the server

UEM

  • JLT-236525 - Changes to log comment on exception
  • JLT-235932 - GeoLocation latitude / Longitude co ordinates were reversed

7.2.10.1019 Resolved Issues

Most critical issues since the last public updates

All resolved issues

Server

  • JLT-235296 - License check might fail when there are multiple .net agents with the same start date on one OS instance and for some license reservations apply and for others not.
  • JLT-235791 - Escape regular expression strings before logging them in case of a fall-back
  • JLT-235072 - Inefficient implementation of MetricGroupReference.isPathBased(..) may cause a Server restart triggered by the watchdog
  • JLT-234771 - "Always send Dynatrace header" setting of a system profile is erroneously kept when the profile is imported to a Server for which the synthetic integration is not enabled
  • JLT-235970 - Fixed: Lost and Found paths can not be followed from parent to child (via "Find distributed PurePaths") in case com.dynatrace.diagnostics.enableCrossSystemProfileSplit is enabled.
  • JLT-235366 - When using forward slashes in RDNs, LDAP users were not able to login.
  • JLT-235297 - Escape double-quotes in regular expressions to handle them correctly in automaton
  • JLT-234786 - SWTException when agent restart dialog is disposed

Server Platform

  • JLT-234421 - BlackDuck scan revealed vulnerabilities in jackson library: update to version 2.9.8
  • JLT-235942 - Adding an agent version mapping for an agent group via REST is denied if the respective system profile is configured to accept webserver agents.

Client

  • JLT-234057 - Webstart Client doesn't start in awt.headless mode on Windows when Webstart tries to open a dialog before actual client start (JDK-8159956).
  • JLT-235171 - Notify the user that NAM releases starting with 2019 no longer offer an AppMon integration
  • JLT-231788 - Don't send legacy UIP data anymore.
  • JLT-235293 - Minor wording improvement for resource dumps
  • JLT-235018 - Potential SWTException due to deferred event handling.
  • JLT-234178 - SWTException when Start Center data response is received after closing Start Center.

PWH

  • JLT-235153 - To avoid data integrity violation duplicates will not be inserted into dynamic measure table.

Correlation and Analysis

  • JLT-235794 - JLT-235794: Allow to disable GAT update on Agent updates, do not change default
  • JLT-235703 - Avoid error when viewing in-progress User Action Purepaths.

Collector

  • JLT-235425 - NullPointerException in SecureRandom.nextBytes(..) when starting a collector on zOS

Session Storage

  • JLT-235964 - JLT-236027: Fix a potential BufferUnderflowException while reading paths

7.2.9.1031 Resolved Issues

Most critical issues since the last public updates

All resolved issues

Server

  • JLT-233864 - On Windows, the CPU model may not be determined correctly since the wmic tool cannot be found
  • JLT-227109 - Temporary missing id for JVM config measure will be logged without stack trace.
  • JLT-234186 - For complex LDAP structures group search depth can be set with the help of a debug flag.
  • JLT-234104 - Deleting a session may throw a ReferenceManagerException
  • JLT-234892 - Unexpected Exception when generating incident mail, possibly missing incident mails.
  • JLT-232856 - Log spam reduced.
  • JLT-234706 - Avoid error after a threaddump was canceled.
  • JLT-230825 - Protect active jre with a directory lock
  • JLT-235024 - Communication with AnalysisServer 7.2.0 - 7.2.7 broken.
  • JLT-233374 - JLT-233374: OSGI cache will not be deleted if interactive mode is set via ini-file or command line parameter.
  • JLT-234303 - When external calls consist of a Webservice and Webrequest node, just the Webservice node was flagged as external. Measures based on such calls may not be calculated.
  • JLT-224977 - Automatically migrate the crypto policy of the installed JREs to unlimited
  • JLT-233937 - Improve error handling in JreFileSyncToCollectorHandler
  • JLT-234183 - Use the latest UEM config for AppMon agents having a version that cannot be mapped to a classic version

PWH

  • JLT-226330 - Detailed error message due to failing performance warehouse connection test.
  • JLT-234340 - Different table names are used on backend and frontend server for detecting UTF16 support.
  • JLT-233680 - ORA-00942 on truncation of temp table on close will be logged throttled without stack trace.
  • JLT-234553 - Leading and trailing white spaces in collector name will be removed. Databases handle trailing blanks differently which might lead to problems.
  • JLT-234052 - Before writing baseline data duplicates will be removed to avoid DataIntegrityExceptions.
  • JLT-227334 - REORG statement added to avoid SqlException.
  • JLT-232204 - Do not log stack trace on frontend server in case of a temporary cache integrity issue.

Client

  • JLT-234896 - Artifacts appear when the size of a dropdown changes in Windows 7
  • JLT-234293 - SWTException if agent platform selection dialog is already disposed
  • JLT-234403 - Changing grouping in web requests dashlet does not hide certain columns that should be hidden
  • JLT-227599 - Potential SWTException in dashboard when toggling Debug Mode.
  • JLT-234897 - Scrolling in dropdowns and the sidebar is not possible on Windows 7
  • JLT-226078 - Graceful error handling for infrastructure dashlets.
  • JLT-235308 - Predefined chart dashlets are named "Chart" when being added to a dashboard

Instrumentation

  • JLT-234481 - Fix error during instrumentation caused by a race condition.

UEM

  • JLT-229122 - ConcurrentModificationException could lead to web requests and user actions not linked to visits in rare cases.

7.2.8.1020 Resolved Issues

Most critical issues since the last public updates

All resolved issues

Mainframe

  • JLT-233976 - Implement failover for the zLocalAgent

Server

  • JLT-232999 - Transformation regexes of end user page action measures are not cached
  • JLT-232519 - Outdated timeseries samples are not properly removed causing memory overhead
  • JLT-233004 - Wrong result description for license reservation consumption GET requests in Swagger UI.
  • JLT-228407 - Agents which were not instrumented due to incompatible JVM flags may be shown as successfully instrumented in the client.
  • JLT-227110 - Parameters are now checked correctly during session Read
  • JLT-233860 - Taking a memory dump using an AppMon agent can fail for very large dumps
  • JLT-233740 - ClassCastException in RealtimeExceptionAnalyzer: ImmutableDynamicMeasureReference cannot be cast to MeasureReference
  • JLT-231405 - JLT-231405: do not check queue-sizes before running reports and on-demand analyzers
  • JLT-232647 - Correct agent resource bundle is only found when fallback is looked up ([DirWatchingAgentResProvider] No exact match for resource bundle version ...)
  • JLT-227336 - Assertion removed.
  • JLT-229618 - IOException because of inconsistent serialization cache
  • JLT-224765 - In case of system profile integrity exception additional diagnosis information will be logged.
  • JLT-231207 - [Performance Improvment] Compare the measure reference in UniqueMeasureIdentifier.compareTo(..) as well
  • JLT-227459 - NullPointerException because splitting value of measure is null: throw an exception early to detect the root cause
  • JLT-221684 - Value of debug flag "enableCrossSystemProfileSplit" synced from server to all collectors to avoid problems with broken PurePaths
  • JLT-233656 - Better resource dump handling when multiple agents have same hostname and PID
  • JLT-216804 - Key of a measure is erroneously null
  • JLT-232854 - On renaming a measure the log message of a missing measure on writing of measurements does not contain the stack trace any longer.

Client

  • JLT-228656 - There are artifacts in trees when moving expandable columns
  • JLT-226128 - Invisible entries are clickable in sidebar
  • JLT-213127 - Improved wording for memory dump progression dialog.
  • JLT-233590 - System profile backups not properly displayed in SysInfo Dashlet if system profile name contains special regular expression characters
  • JLT-225211 - Details in business transactions dashlet table cannot be shown
  • JLT-232976 - "Contribute to the Dynatrace Community" link redirects to a none existing page
  • JLT-226252 - Improved handling of client request errors
  • JLT-229357 - Fixed NPE in APIHierarchyRenderer
  • JLT-225706 - Sanity check for EditableTree
  • JLT-231895 - Measure renaming not working: "did not find expected measure center data to rename"

UEM

  • JLT-192808 - User Interface issues to do with the PureLytics configuration screens
  • JLT-233492 - Added additional correlation logging to monitor what happens when test cases have web requests not getting linked to parent actions
  • JLT-230633 - When using the User Experience setting to include visits only from specific IP Addresses AND the client IP address was being passed though a header AND that header contained a comma separated list where the first address was preceded by a space THEN no visits would be created.

Correlation and Analysis

  • JLT-234097 - Do not mark PurePath corrupted if meta-data on sub-path exception stack-trace cannot be resolved.
  • JLT-224809 - Fix incorrect record limit in PurePath Dashlet

WebUI

  • JLT-231577 - Visits from the German regions Baden-Württemberg and Thürigen are not shown in the world map.

PWH

  • JLT-230745 - Sending of status re-connected which was introduced with JLT-220404 is turned off on default.
  • JLT-234100 - Behavior implemented with JLT-219343 is no available on frontend server too. This prevents inconsistency of the cache.
  • JLT-225891 - Diagnosis information added if the id for a config measure could not be determined.
  • JLT-232504 - POstgreSQL: added debug flag to try a different "check if temp table is present" strategy
  • JLT-234175 - Assertion removed which is obsolete now because of JLT-234100.
  • JLT-234051 - Id of a dynamic measure will be replaced in cache if it does not match the current value.
  • JLT-225739 - Minor modification to make a unit test pass for MySQL.

Collector

  • JLT-233512 - Improved logging of AppMon Agent request issues.
  • JLT-227990 - Misleading error message in log
  • JLT-232229 - Do not restart the Collector after update installation if automatic Collector updates are disabled

Server Platform

  • JLT-233290 - Swagger REST documentation doesn't display in IE11 because of unsupported JavaScript syntax

Agent

  • JLT-230169 - PHP Windows support added for php version 7.0 to 7.2

Tests

  • JLT-232507 - System profile synchronization to agents is flaky in CI

Java Agent

  • JLT-225846 - ITRA sensor sets tagId -1 so subpaths don't correlate

.NET Agent

  • JLT-225444 - Sensitive pathnames are now handled correctely

7.2.7.1014 Resolved Issues

Most critical issues since the last public updates

All resolved issues

Client

  • JLT-233061 - SWTException because button is already disposed in the metric browser dialog
  • JLT-232985 - Exception when repeatedly editing the same schedule include.

UEM

  • JLT-231615 - NPE could lead to missing visit data
  • JLT-230821 - Unnecessary log spam in case of a null HTTP response.

PWH

  • JLT-232129 - To mitigate an Oracle issue a redundant "GROUP BY" clause can be turned off via a debug flag. Another solution is to set a parameter of the Oracle DB: _OPTIMIZER_AGGR_GROUPBY_ELIM=false.

Server

  • JLT-232243 - Webserver agent data (sometimes) skipped after master agent reconnects to a different collector

7.2.6.1034 Resolved Issues

Most critical issues since the last public updates

Agent

  • JLT-231809 - zRemoteAgent crash when DB2 aggregation is enabled.
    • Impact: zRemoteAgent instability and crashes.
    • Cause: A DB2 Aggregate object was deleted, but a cached reference to it was not set to null, and later it was used, causing memory corruption
    • Solution: If the aggregate object being deleted is pointed to by the cached ptr, null out the cached ptr.

All resolved issues

Server

  • JLT-232226 - Add "Location" by default to the response headers to be captured in the web request sensor configuration.
  • JLT-231761 - Close session export output stream quietly
  • JLT-226248 - NPE because business transaction has no measure reference
  • JLT-230664 - Add endpoint to modify consumption of license UEM and Agent Hour reservations via REST.
  • JLT-231548 - Decreased Purelytics queue sizes to low memory situations on the frontend server in case of a slow database
  • JLT-229858 - Collector is not provided with missing agentres file if it is not running on the same major.minor version as the Server
  • JLT-232621 - For the self monitoring measure of latency between server and collector nano seconds will be used to be robust against system time modifications.
  • JLT-231210 - In rare cases, schedules are not executed that are configured with an end time relative to the start time.
  • JLT-230834 - External call detaction fails when an observed tier is a leaf tier.
  • JLT-229672 - Duplicate concurrent execution of server shutdown routine
  • JLT-231272 - Slightly increased session storage queue size for XLarge32 and XLarge64 memory categories Slightly increase realtime analysis queue size for XLarge64 memory category
  • JLT-231515 - Agent Hour reservations are not handled correctly, causing reservations to possibly not get their assigned volume.
  • JLT-224937 - AppMon self-monitoring agent uses a version that cannot be mapped
  • JLT-230855 - Fix-up nodes on AppMon agent paths that consist of only link- and deactivated nodes to ensure, that meta-data (string/method) references have been replaced by actual meta-data prior to path storage.
  • JLT-231545 - Do not run tier detection when reanalyzing sessions because it is not useful there.
  • JLT-230885 - The configured case sensivity of PWH will be logged on startup.

Client

  • JLT-231333 - Column sorting is not applied when table data is filtered
  • JLT-230992 - Prevent throwing of exceptions if outdated items (version < 7.1) are pasted to the Client
  • JLT-232617 - Logged error when closing Incident Rule Editor window
  • JLT-232130 - Incorrect platform switch message is shown in Agent Overview if agent updates are disabled
  • JLT-231003 - Potential IOException when trying to determine IE version during Client startup.
  • JLT-225021 - Canceling a monitor edit dialog after renaming a monitor may corrupt the corresponding system profile
  • JLT-228808 - Add OpenKit integration for Client-Server-Requests and enable OpenKit by default.
  • JLT-231458 - Access denied exception prevents Client update
  • JLT-231259 - Error loading system profile leads to silent failure for some actions in Incident dashlet.
  • JLT-226462 - Do not throw exceptions if outdated items (e.g., system profiles) with a version less than 7.1 are pasted to the Client
  • JLT-231618 - In the geographical locations section of the server settings the client IP address and server host name configuration would no longer after configuring geographical locations.
  • JLT-231614 - Potential NullPointerException in TabFolder when handling mouse click.

PWH

  • JLT-231213 - Improved handling of agent names which exceeds the maximum length of database column.
  • JLT-232078 - Do not cache dynamic measures with database id = 0.
  • JLT-231253 - Handling of UTF16 characters in application improved in case the database encoding is only single byte character.
  • JLT-225072 - Dynamic measures with trailing blanks in agent host, application or key id will not be cached to avoid cache conflicts.

WebUI

  • JLT-228039 - Fixed missing step id and step name in query param for synthetic tiles

Agent

  • JLT-231809 - zRemoteAgent crash when DB2 aggregation is enabled.

Correlation and Analysis

  • JLT-228028 - Support for transactions sent by AppMon agent in sub-path V2 format (future proofing).
  • JLT-231443 - Prevent log spam due to erroneously sends MT1/MT2 mobile tags.
  • JLT-232088 - Unify JMS destination type for appmon and classic agents.

Collector

  • JLT-231512 - NullPointerException when a previously deleted update is reinstalled
  • JLT-231505 - JLT-231505: Add debug logging for Agent overdue handling
  • JLT-231508 - Removed Java 10 & Java 11 enum on the Collector for AppMon classic Agents, as it may result in errors during rollback

Charting

  • JLT-230635 - Measure count for a fixed timeframe changes if the resolution of the chart is changed
  • JLT-230455 - Incident heat field would only show a single incident if multiple incidents occurred for the same incident rule simultaneously.
  • JLT-231381 - Chart rendering could fail after making changes to the chart configuration

UEM

  • JLT-231639 - Updated UEMDatabase to 1.0.28 and added 'South Korea' as an alternative name for 'Republic of Korea'

Session Storage

  • JLT-231549 - JLT-232518: the size of the visit session-storage queue now depends on the memory sizing.

7.2.5.1022 Resolved Issues

Most critical issues since the last public updates

Server

  • JLT-230748 - Memory leak on backend server and missing Visit data in WebUI
    • Impact: Memory leak on backend server, Missing Visit data in WebUI
    • Cause: PureLytics Visit data has not been flushed into PWH on a regular basis.
    • Solution: Ensure Purelytics Visit data is flushed on a regular basis.

All resolved issues

Session Storage

  • JLT-230738 - Disable cross-server search bloom filter by default to reduce backend memory usage

Server

  • JLT-231465 - JLT-231415: Too much PWH activity and high Frontend Memory Usage caused by wrong Purelytics flush interval
  • JLT-215175 - Storing a system profile should be robust against exceptions thrown during the storage process
  • JLT-231174 - ArrayIndexOutOfBoundsException on pre-7.2.3 clients with a 7.2.3+ server
  • JLT-230714 - Additional diagnosis log messages added.
  • JLT-229997 - Improved logging while loading installed jres
  • JLT-229471 - Always delete the OSGi folder if interactive mode is enabled.
  • JLT-230748 - Memory leak on backend server and missing Visit data in WebUI
  • JLT-229823 - Adapt log message for unoptimizable regular expressions
  • JLT-230724 - Slow server startup if infrastructure has a very large number of hosts

Client

  • JLT-228644 - When configuring the agent version for an agent with a version lower 7.0 a "NoSuchElementException: No agent resource for ..." may happen on the Backend Server
  • JLT-230293 - Potential NullPointerException in License Volume Import Wizard when entering wrong credentials.

Collector

  • JLT-206186 - AgentResourceManager may cause a log spam at the startup of the Collector
  • JLT-225524 - OpenJDK 8 AppMon classic agents caused a warning log on the collector
  • JLT-230752 - After a rename of a system profile, all monitors in the system profile stop sending measurement data until next storage of the renamed system profile.

Integration and Services

  • JLT-229954 - It was possible to send malformed metric ids to dynatrace, where the metric id would start with a number.

PWH

  • JLT-230791 - Temporary tables will be truncated after usage. This is an additional step to make sure that no data is left to the next transaction. Actually this additional step is not necessary since it is ensured by the database in general. However, with Oracle error ORA-00942 was observed on the mentioned step. In this case the error will be logged throttled and a statistic counter will be increased and periodically logged. No PWH incident will be fired.

UEM

  • JLT-230275 - UserActionPurePath Dashlet fields Threshold ms, Performance Value ms and threshold Factor where not being processed as the correct type. As a result their corresponding fields in the XML report (baseline, perf_metric_value and ux_threshold_factor) were not getting saved to the report.

7.2.4.1039 Resolved Issues

Most critical issues since the last public updates

  • JLT-230748 - Memory leak on backend server and missing Visit data in WebUI.
    • Impact: Memory leak on backend server, Missing Visit data in WebUI.
    • Cause: PureLytics Visit data has not been flushed into PWH on a regular basis.
    • Solution: Ensure Purelytics Visit data is flushed on a regular basis.

All resolved issues

Server

  • JLT-229354 - Improve synchronization behavior of jre update on local host
  • JLT-229666 - Prevent NullPointerException in RemoteJobCenter
  • JLT-229861 - Add a random number to the system profile backup file name
  • JLT-226077 - Prevent mismatch between regex configured in web-request configs and those encoded in the regex engine
  • JLT-224168 - Log Spam reduced in case a JVM metrics get lost under high server load
  • JLT-227986 - Increase timeout for java property reader
  • JLT-216337 - Prevent IllegalStateException during server shutdown
  • JLT-229323 - Log spam in DefaultApiMeasureProvider: "Measure could not be found"
  • JLT-229877 - Reduce log spam in SingleProfileMeasureCenter
  • JLT-229639 - Log spam in RealtimeRemotingAnalyzer: "unable to handle remoting attachment"
  • JLT-225957 - NPE check added to avoid NullPointerException
  • JLT-226087 - Introduce debug flag to set a specific jre preference
  • JLT-222205 - Server failed to create a backup file for system profile
  • JLT-229862 - JLT-229862: Missing Visit data in WebUI after PWH aging task run
  • JLT-210934 - Introduction of self monitoring measure for the duration of a pure path-container in the RTA queue
  • JLT-227123 - Allow xlarge512 sizing whenever Java 11 or higher is active
  • JLT-198177 - Combined renaming of system profile and master monitor causes inconsistent state of monitor in PWH. Added missing code that handles system profile rename in master monitor configs.
  • JLT-228921 - Unexpected agent version may be shown if the configured rollout is used in combination with an AppMon agent
  • JLT-229403 - Prevent deletion attempt of active jre

PWH

  • JLT-225710 - Size of test data to detect UTF16 encoding reduced to avoid integrity violation.
  • JLT-225626 - Diagnosis information added in case a measure could not be synchronized with PWH.
  • JLT-215936 - In case writing to database timed out, additional information will be logged and statistic data will be gathered.
  • JLT-228798 - Log spam reduced in case repository is not connected.
  • JLT-225247 - Additional log message introduced to avoid complete stack trace in case writing to PWH failed because connection was lost.
  • JLT-223610 - Support of upper and lower case characters in keys of splittings added.

Client

  • JLT-230183 - Metrics are missing in process details view for Azul Zulu VMs
  • JLT-230105 - Trying to import an empty dashboard file might lead to a NullPointerException.
  • JLT-229330 - Update installation on Client may be skipped erroneously
  • JLT-220605 - Business Transaction Hotspot dashlet hangs on "Expand All" and "Collapse All"
  • JLT-229402 - Prevent Java update synchronization while installing fixpack
  • JLT-230108 - AppMon RCP: Serialization error on fetching DBAgent's lock info
  • JLT-230023 - Server, system profile and dashboard picker do not open on multi-monitor setups on Linux
  • JLT-228048 - Thresholds of 'Failed Transaction Count' and 'Failed Transaction Percentage' measures getting reset after modifying Business Transaction
  • JLT-170654 - Prevention of missing Pure Path on drill-down based on path identifieres.
  • JLT-227232 - Value specified for attribute spentityid in sso.config.xml is now kept when editing single-sign on settings in client.
  • JLT-229324 - Improve stability of java update installation

Charting

  • JLT-229668 - Chart dashlet does not render a chart when changing settings during a refresh

Integration and Services

  • JLT-228738 - [Dynatrace Integration] When an AppMon measure name starts with a non-alphanumeric character, it resulted in an illegal dynatrace metric name.

Collector

  • JLT-228817 - Initial detection of unreachable server via HTTP communication takes too long after Collector startup if connection runs into timeouts
  • JLT-229879 - If JavaScript Agent reportUrl property is configured via custom configuration properties, it gets duplicated in the agent configuration.
  • JLT-229674 - Attempted to put empty file into file download cache, which is not supported by the cache.
  • JLT-192216 - Improved synchronization/isolation between update and serialization of job center events
  • JLT-225058 - Scheduler throws "JobPersistenceException" when an unknown trigger is selected immediate for execution. Changed behavior to first check if the trigger exists, perform the execution only if it exists and issue a meaningful log message if it is not existing.

Correlation and Analysis

  • JLT-228967 - Do not link subpaths to a linknode in case the linknode doesn't have a sane start date.
  • JLT-229405 - Limit the number of SubPaths for a PurePath (1000 per default) to prevent problems with deeply nested subpath graphs.

Server Platform

  • JLT-228240 - Launcher uses original JVM if the JVM from an update could not be started.

Communication

  • JLT-225395 - Communication stability improvement to avoid dropped messages in rare cases.

UEM

  • JLT-229136 - Updated uemdatabases to version 1.0.25

7.2.3.1030 Resolved Issues

Most critical issues since the last public updates

All resolved issues

PWH

  • JLT-213015 - Additional log information added on fetching Ids for measures.
  • JLT-225485 - Splittings which exceeds the maximum length of the corresponding column in PWH will not be cached. This prevents inconsistency of the cache.
  • JLT-225886 - Additional log information added on synchronization of measures with PWH.
  • JLT-219343 - Splittings containing UTF16 characters will not be cached if UTF16 is not supported by the db schema. This prevents inconsistency of the cache.
  • JLT-228238 - Fix closing incidents with wrong end time during repository connect.
  • JLT-226287 - Using defensive copy of subscribed measures on synchronization of measures with PWH. This prevents race conditions.
  • JLT-215749 - Null pointer check added to avoid NullPointerException on accessing PWH
  • JLT-227332 - Debug flag introduced and defaulted to false to suppress diagnosis log message.

Correlation and Analysis

  • JLT-228972 - JLT-228972: fix problem with on-demand analyzer result limit when system profile name contains a dot
  • JLT-227594 - Fix logspam when subpaths get removed from their parent paths in case they run into the maximum age
  • JLT-228739 - Correct subscribed dashlet filter statistics.
  • JLT-228247 - Prevent override of application name detected on entry sub-path by application name detected on descendant sub-path.

Server

  • JLT-228241 - Deletion of the active JRE
  • JLT-211959 - Legacy code removed which was used in fix JLT-211959 for asserting the new new implementation.
  • JLT-228753 - Improve timeout duration and messages for AppMon Agent Hot Sensor Placement.
  • JLT-226910 - Slow Data Warehouse led to increased memory consumption on Frontend Server
  • JLT-227992 - Improved error handling for unexpected thread dump message.
  • JLT-221077 - Null pointer check added to avoid NullPointerException in RTA.
  • JLT-228540 - Fixed memory management log spam
  • JLT-228978 - PurePaths sent within the first 10s after startup of an AppMon agent (Classic agent was not affected) might not be correlated
  • JLT-208682 - The fallback for JLT-206429 fix is no longer needed and was removed.
  • JLT-228852 - In case an host is referenced by multiple alerts it now time-out correctly
  • JLT-228660 - Set "-Xshare:off" in the update.ini files to ensure the self-monitoring Agent works properly when Java 11 is used

Client

  • JLT-224952 - Potential SWTException when editing search text in source picker dropdown and quickly closing it.
  • JLT-227860 - Make it configurable that an agent group restriction on a measure is not automatically applied to the copy of the affected agent group
  • JLT-226135 - Dropdowns embedded into a table would be shown in separate dialogs on Linux.
  • JLT-225246 - Multiple NullpointerExceptions potentially being thrown when client is shut down while refreshing dashboard list in background.
  • JLT-228051 - Client cannot connect to Server after update installation
  • JLT-227124 - The Webstart Client is not automatically restarted after an update was installed
  • JLT-227460 - Potential NullPointerException in PortletWorkerJob.isCanceled().
  • JLT-226320 - macOS client crashed
  • JLT-225034 - Buttontext not fully visible in license settings on linux.
  • JLT-225230 - Text of grouping column cut off in Tree on Linux when it's not first column.
  • JLT-228919 - Warning that a non-existing image was tried to be released.
  • JLT-225966 - Unclear message when trying to deactivate a license that has already been terminated in eServices.
  • JLT-222758 - Potentially missing data in tree when refreshing and manually sorting at the same time.
  • JLT-225210 - Client runs out of handles when quickly pasting a lot of dashlets
  • JLT-226132 - Option for exception exclusion rules was shown for PHP exceptions even though it is not supported for PHP.
  • JLT-225251 - Potential deadlock when a remote proxy script is configured in system settings.
  • JLT-228582 - UIP Events fill openkit queue causing an IllegalStateException.
  • JLT-227117 - Toolbar dropdowns use more UI-resources than needed
  • JLT-225224 - Potential IllegalThreadAccess in SourceReferenceSelectionComponent when server connection is canceled or fails.
  • JLT-226127 - The last server is no longer visible in the Dynatrace Server Settings dialog after adding a new server
  • JLT-228789 - Text truncation in dropdown does not work
  • JLT-227335 - Potential SWTException when checking Thread access during shutdown of client.
  • JLT-228648 - Drill down from chart doesn't work for measures that are calculated for multiple agent groups.
  • JLT-228227 - Manual deactivation of communication ports isn't considered for HTTP connector health information for 7.0 collectors

Tests

  • JLT-227546 - When using default shipped expired legacy certificates at first connection, connection can be established.

WebUI

  • JLT-227745 - Custom timeframe picker in advanced settings is sometimes partly hidden.
  • JLT-228047 - In the world map visits are not correctly mapped to the Spanish region "Galicia".
  • JLT-226249 - Migration of old dashboards fails in some cases.

Collector

  • JLT-228398 - Do not log the stack trace if an UnsupportedAgentPlatformException happens
  • JLT-228530 - Do not load the self-monitoring agent on non-x86 platforms
  • JLT-228560 - Only enforce Java version preconditions for updates on x86 architecture

Charting

  • JLT-229065 - Color in color column of chart dashlets is not shown on Linux.

Java Agent

  • JLT-227001 - Apache Http Client 3.x: argument of executeMethod null when no URI is passed

Server Platform

  • JLT-224559 - Cron schedule accepted by the alert suppression REST API is not parsed correctly and therefore incorrectly presented in both Rich Client and REST API.
  • JLT-227000 - REST API for Business Hours allows to input illegal time spans rejected by the scheduling framework (start time of day after end time of day)

Mobile

  • JLT-225715 - Remove maxMobileCrashesSentPerMin from client and server

Communication

  • JLT-227993 - High overhead in System Profile List dashlet due to sending full system profiles.

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.