Update 2

2017-07-04

A new update for Dynatrace AppMon 2017 May 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!

Resolved Issues

This update contains all changes of:

  • Public update 6.5.18 and earlier (not affected by JLT-192329)
  • All updates released for versions 6.3 and earlier

7.0.2.1011 Resolved Issues

Most critical issues since the last public updates

Mainframe

  • JLT-190358 - zRemoteAgent crashes when processing capture-type BCD
    • Impact: zRemoteAgent crashes when processing capture-type BCD
    • Cause: zRemoteAgent crashes when processing capture-type BCD
    • Solution: Fixed an issue with zRemoteAgent incorrectly parses the capture-type BCD causing it to crash.

Correlation and Analysis

  • JLT-192304 - Fix NPE happening due to a race condition which was introduced in 7.0.1
    • Impact: Affected subpaths can never complete.
    • Cause: Usage of a reference after the memory barrier.
    • Solution: Fix order of statements.

All resolved issues

WebUI

  • JLT-189398 - Memory charts for HP-JVMs are not shown.
  • JLT-191982 - [WebUI] Properly handle owner information when deleting a dashboard
  • JLT-189410 - Keypress check in WebUI blocks entering into number fields on french keyboards
  • JLT-191273 - Open-end drilldown timeframe is not properly displayed in the filterbar
  • JLT-189698 - Bar chart bars aren't rendered correctly with high tile resolution on a small screen resolution.

Collector

  • JLT-191599 - .NET Agent - ADO.NET Connection Pool attachment reported workstation id, instead of database name when the keyword 'database' was used in the connection string.
  • JLT-187076 - No more agent connections possible, "Unable to create connection for request ..." in log.
  • JLT-189564 - Agent property "agent.basename" not set on agent recovery

PWH

  • JLT-189077 - Add possibility to skip validation of entered performance warehouse configuration data.
  • JLT-192357 - Improved collision detection for performance warehouse migration.
  • JLT-190959 - Fixed default strategy for embedded performance warehouse.
  • JLT-192489 - Improved performance of repairing inconsistent data in performance warehouse during migration.
  • JLT-189338 - Improve caching in lookup tables.
  • JLT-190086 - Improved exception handling for performance warehouse.
  • JLT-186179 - Possibly server not starting due to Performance Warehouse connection issue.
  • JLT-192616 - Improve the 7.0.0.8 performance warehouse migration step to resume after a failed execution.

Server

  • JLT-188303 - No 'Continuous transaction recording was aborted' incident will be created if there is already one open.
  • JLT-187280 - Thread Dump on server stays in-progress until server restart in case monitors and/or threads change during Thread Dump creation.
  • JLT-189134 - Prevented server restart by fixing session synchronization bottleneck with large amount of sessions.
  • JLT-190564 - SSO: validation of Identity Provider Certificate fails
  • JLT-191887 - Potential NPE in ActionCenterCheck
  • JLT-190078 - Support DCRum integration in new correlation out of the box.
  • JLT-191363 - Mimimal external measures' timestamp populated to test execution if not provided
  • JLT-189677 - Global incident downtimes do not activate correctly.
  • JLT-189719 - Ensure that the bytecode of java proxy classes are not written to the classcache
  • JLT-187531 - Fix a potential BufferUnderflow exception while reading incidents from sessions.
  • JLT-188618 - Fix an Exception when reading path attachments from session-storage
  • JLT-190777 - Make recommended cpu cores of sizing global changeable via debug flag.
  • JLT-191306 - Null pointer check added to mitigate JVM crash.
  • JLT-191700 - Reduce performance overhead for calcuation of the Failed Transaction and Failed User Action Count measures
  • JLT-189572 - Prevent manually editing of unsupported sizings in ini file.
  • JLT-188082 - Controlled rollout based on Host + Agent Name does not work for Web Server OneAgents that were migrated from AppMon
  • JLT-187038 - Server log spam: if password was wrong don't log a stack trace anymore
  • JLT-191419 - Improved detection of server health to avoid early discarded PurePaths, especially in environments with many system profiles.
  • JLT-190607 - Add additional log output in case measure reference is null
  • JLT-191415 - Security vulnerability found in Apache POI version used by AppMon
  • JLT-188678 - Table order of resource-dump warnings table not correctly restored.
  • JLT-189128 - Added log output for enabled TLS ciphers and protocols
  • JLT-178235 - Potential keystore corruptions due to frequent unnecessary and non-atomic write access. Missing automatic restore mechanism when keystore is corrupted.
  • JLT-189404 - Incorrect log supression in MultiMessageBroadcaster
  • JLT-190156 - Combined weekly/monthly schedule exclusions containing one "exclude" all schedule cause unexpected schedule behavior like scheduled executions unexpectedly ending after a week or month.
  • JLT-192133 - Markin Lost and found transactions as corrupt can be disabled now.

Client

  • JLT-190900 - Add tier wizard for Node.js was not supporting Windows
  • JLT-188619 - Prevent NullPointerException when opening stored TestAutomation dashlet
  • JLT-189545 - Scrollbars in nightmode are misplaced in some instances.
  • JLT-191848 - Error shown when creating Measures from PurePath nodes generated by web server OneAgents.
  • JLT-188190 - Wrong Agent Platform configuration may be shown in Agent Overview after server restart
  • JLT-189148 - Synthetic Monitoring: Disable 'Data feed' and remove configuration UI as desupported by Synthetic
  • JLT-189974 - Misleading percentage in Transaction Flow when there are First Party Calls.
  • JLT-189659 - Prevents potential null pointer exception when storing a system profile
  • JLT-183715 - Client sometimes throws SWTException about a disposed widget in the deployed certificates tab

Charting

  • JLT-190108 - Incident chart does not allow chart splitting of more than ten incident rules.

Correlation and Analysis

  • JLT-191984 - Check argument for null to avoid a late NPE.
  • JLT-188758 - Paths from OneAgents that run into a timeout are marked as corrupted.
  • JLT-189566 - Fix waiting for string resolution of mobile tags.
  • JLT-192615 - Elapsed time column doesn't show values for paths from OneAgents.
  • JLT-191125 - Fix propagating CICS Transaction ID to a captured argument.
  • JLT-188749 - Simultaneous linking during UEM correlation and modification of sub-path transaction from sub-path correlation engine may lead to CME and consequently dropped user actions.
  • JLT-192112 - Fix race condition with UEM for paths from OneAgents.
  • JLT-192304 - Fix NPE happening due to a race condition which was introduced in 7.0.1

Java Agent

  • JLT-189425 - Added cassandra sensors early return in case of disabled bind value capturing
  • JLT-189699 - Groovy methods that previously would show in PurePaths don't show anymore after upgrade to 6.5 - add debugEnableGroovyNative, so groovy.lang.GroovyObjects, groovy.lang.Scripts and groovy.lang.Closures may be instrumented again (although not supported)

UEM

  • JLT-172631 - NullPointerException in ActionDefinitions.isKnownAction(..)
  • JLT-191305 - Onreadystatechange events of XHRs are fired multiple times in rare cases on IE, if the agent is injected asynchronously.
  • JLT-191148 - Visit mapped to IE7 when IE11 compat mode was used (Trident/8.0 user-agent)
  • JLT-188390 - Using incremental responses with XHRs leads to readyState 3 events not always firing, thus information is received too late.

Nginx

  • ONE-8408 - Non-ASCII characters in the request URI path are shown as '?' in the PurePath.

Instrumentation

  • JLT-189009 - Fix synchronization bottleneck in instrumentation of .net agents.

Mainframe

  • JLT-190358 -

DB Agent

  • JLT-189160 - DB2 explain plan retrieval leaves rows in temporary tables
  • JLT-191944 - Expanded error message on failing to retrieve explain plans for truncated SQL on MySQL
  • JLT-188091 - DB Agent Live View slow queries issue with large databases - improved logging
  • JLT-190879 - DB2 connection validation — missing permissions to explain plan tables prevented db2 agent creation
  • JLT-190593 - DB2 dataaccess permission made optional: may be replaced by access to all required views and functions (see Database Agent configuration section in AppMon documentation)

.NET Agent

  • JLT-188426 - Handle Leak when invoking .NET Thread Dump. Could lead to timeouts of Thread Dumps unter certain curcumstances.

Dashboard

  • JLT-190028 - The "Start Time" field was missing when exporting User Action PurePaths to XML

Server Platform

  • JLT-179651 - Improved log for ArrayIndexOutOfBoundsException in CachingTimeSeries.

Session Storage

  • JLT-190248 - Fix NPE on session analysis.
  • JLT-190800 - Visits potentially not stored after maximum storage queue size has been reached although queue size already below maximum again.

Most critical issues since the last public updates

Mainframe

  • JLT-188429 - zRemoteAgent crash when 2 zdcs connected to a single zRemoteAgent hook the same IMS regions
    • Impact: zRemoteAgent crashes.
    • Cause: The 2nd zdc's INIT deleted the objects owned by the 1st zDC.
    • Solution: Don't hook the same IMS regions with different zDCS pointing to the same zRemoteAgent.

.NET Agent

  • JLT-188684 - The agent might cause a System.NullReferenceException for C++/CLI delegates, when the .NET thread tagging sensor is activated.
    • Impact: Instrumented application crashes when a new .NET Thread object with a C++/CLI delegate is created.
    • Cause: A missing null check for the declaring type of a C++/CLI delegate, which might be null.
    • Solution: Added null check to avoid possible System.NullReferenceException.

UEM

  • JLT-190912 - Custom geographical location city in visits dashlet are not able to be set as a splitting after upgrading to 7.0
    • Impact: The region for GeoLocations defined for United States (US) and Canada (CA) was missing after upgrading from 6.5 to 7.0
    • Cause: In 7.0 region codes were determined through using the UEMDatabases APIs as opposed to a look up in a local table. This provided better flexibility and enabled region code changes to be reflected quicker. However, regions for USA and Canada were now returned using ISO codes as opposed to FIPs codes. Since 6.5 saves GeoLocations in the IPMappings with region codes in FIPs this caused them to be missing when splittings were performed and when the GeoLocations were edited.
    • Solution: A small lookup table for converting FIPs to ISO for US and Canada is now used. When a GeoLocation region code is resolved to it's name, the code is first checked to see if it is a FIPs code and if so converted to its equivalent ISO code.

Collector

  • JLT-191365 - Java 8 instrumentation may result in Illegal use of nonvirtual function call VerifyErrors
    • Impact: The application might not start up or certain features might not work.
    • Cause: Lambda generated classes were instrumented when the calling class was not, resulting in VerifyErrors.
    • Solution: Classes that may result in the exception are excluded from instrumentation.

JavaScript

  • ONE-8013 - Source & Target URL are not shown as expected for soft page navigations Store sourceURL on user input object for better SPA support
    • Impact: source URL appears the same as target URL when history API is used for soft page navigation actions
    • Cause: the page information is collected too late for XHR actions
    • Solution: collect the url and title at the time of user input collection rather than action creation

All resolved issues

Collector

  • JLT-180298 - Controlled rollout in host-mode does not work if the bootstap agent sends a name containing square brackets
  • JLT-180591 - Connection Pool Attachment not present when Exception happens on DB-Open (leads to databases)
  • JLT-188090 - Additional debug properties to fine-tune connection timeouts.
  • JLT-189087 - Fix Collector NPE that can happen during shut down
  • JLT-189427 - Remove ReactiveX exclusion rules
  • JLT-191365 - Java 8 instrumentation may result in Illegal use of nonvirtual function call VerifyErrors

MessageBroker Agent

  • JLT-183797 - Early Discarded Purepaths for WSAs - Empty Root Path

Server

  • JLT-186249 - Changing the calculation of the "Application process unhealthy" incident to prevent false/positives and trigger more reliable
  • JLT-187542 - Log spam "Got subscription for dynamic measure with missing parent" after measure overload/explosion situation
  • JLT-188872 - Adding volume voucher id to volume deactivation key.
  • JLT-189312 - Fixed NPE that can happen when trying to chart from a stored session
  • JLT-189638 - Fix ephemeral NPE in server (can happen during server shutdown, cosmetic only)
  • JLT-190188 - Purepath details xml reporting issue

Correlation and Analysis

  • JLT-188318 - Missing sub-path node amount limitation may lead to memory problems, if high amount of nodes is received per sub-path from OneAgent in short time (sub-path message correlation).
  • JLT-188384 - Support captured argument index of OneAgents.
  • JLT-188388 - Missing PurePath node limitation may lead to memory problems, if PurePath link depth is shallow compared to node count and high amount of nodes is received per sub-path in short time (both event- and message sub-path correlation).
  • JLT-189960 - Missing PurePath link depth limitation may lead to memory problems, if high amount of short sub-paths is received and linked in short time (both event- and message sub-path correlation). For example, corresponding PurePath structures are created when using reactive frameworks where each task schedules a new task before finishing execution.
  • JLT-190439 - Throttle log when duplication SubPathMessages arrive at the server.

UEM

  • JLT-188392 - UEM DB seems to have troubles with chinese characters
  • JLT-189222 - Server: java.lang.StringIndexOutOfBoundsException
  • JLT-189416 - Speed index must not be an option for AJAX actions
  • JLT-190018 - Legacy bootstrapper isn't delivered with correct version format, thus fallback agent will be injected.
  • JLT-190912 - Custom geographical location city in visits dashlet are not able to be set as a splitting after upgrading to 7.0

Mainframe

  • JLT-188429 - zRemoteAgent crash when 2 zdcs connected to a single zRemoteAgent hook the same IMS regions
  • JLT-189774 - The zDC is not notified when a CICS/IMS region becomes unresponsive.

.NET Agent

  • JLT-188684 - The agent might cause a System.NullReferenceException for C++/CLI delegates, when the .NET thread tagging sensor is activated.

Webserver Agent

  • JLT-188768 - Apache crashing at start on limited environments where the process command line cannot be determined.

PWH

  • JLT-188865 - Improve aging task.
  • JLT-189297 - Improved performance warehouse migration.
  • JLT-189345 - Prevent unnecessary measure booking.
  • JLT-189667 - Correct handling of connection state during failed performance warehouse reconnect.
  • JLT-189887 - Fixed state handling during performance warehouse migration.
  • JLT-190575 - Add special handling for new jdbc driver

Client

  • JLT-189092 - Client UI slowdown when opening incident configuration with a very high number of condition measures.
  • JLT-189127 - Dashlet filter may not work correctly after renaming a business transaction
  • JLT-190534 - Import License Wizard does not list DB agents

Integration and Services

  • JLT-189402 - Persist all pending TestAutomation data before fetching TestRun results

Plugins

  • JLT-190598 - "Unix System Monitor" plugin cannot connect through SSH when legacy MAC algorithms are not accepted by the SSH server (separate download)

Mobile

  • ONE-1468 - Android Agent: Switched agent network communication from Apache HttpClient to HttpUrlConnection
  • ONE-7414 - iOS Agent: Improved crash signal handling.
  • ONE-7471 - iOS Agent: improved capturing of bytes send/received
  • ONE-7718 - iOS Agent: improved manual webrequest timing
  • ONE-7934 - iOS Agent: Improved action view name handling
  • ONE-8004 - iOS Agent memory leak during agent initialisation
  • ONE-8011 - iOS agent: webrequest to localhost was reported during first agent initialisation

Core

  • ONE-7376 - Windows metrics only: Error information is not correct, when accessing network interface data fails.

JavaScript

  • ONE-8013 - Source & Target URL are not shown as expected for soft page navigations
    • Store sourceURL on user input object for better SPA support