Skip to end of metadata
Go to start of metadata

 2017-07-24

A new update for Dynatrace AppMon 6.5 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

6.5.21.1016 Resolved Issues

57 (+ 2) critical issues, 783 (+ 23) total resolved issues

 Component change overview
ComponentTotalNew
.NET Agent100
Agent150
Charting11
Client972
Collector490
Common20
Communication20
Core10
Correlation and Analysis310
DB Agent61
Dashboard10
Installer and Build20
Instrumentation10
Integration and Services10
Java Agent250
JavaScript21
JavaScript Agent43
Mainframe261
MessageBroker Agent50
Mobile476
Nginx10
PWH311
Plugins41
Runtime Diagnostics130
Server2313
Server Platform30
Session Storage10
UEM1093
WebUI370
Webserver Agent250

Most critical issues since the last public updates

JavaScript

  • ONE-8536 - Angular JS monitoring breaks our web app
    • Impact: Page cannot load (many angular injection errors are thrown)
    • Cause: Broken $httpProvider dependency caused by our angular injection
    • Solution: do not insert our angular dTModule as a dependency for other modules whose dependencies include angular defined "ng" modules.

Mainframe

  • JLT-193549 - Memory leak in zRemoteAgent when IMS subagents are connected
    • Impact: Very large memory leak in the zRemoteAgent when IMS subagents are connected
    • Cause: Exit event handling was not freeing (repooling) the associated method object created during Enter event handling. Only for IMS
    • Solution: Remove the isCICS check so that IMS methods are freed or repooled.

All resolved issues

Charting

  • JLT-166073 - Chart dashlets in the AppMon rich client don't show data for the whole timeframe under certain circumstances.

DB Agent

  • JLT-193520 - MySQL slow queries list slowest of least executed queries

Plugins

  • JLT-192825 - NTLM authentication in URL Monitor plugin not working after redirect to different host

UEM

  • JLT-192492 - Splitting measure "Visits - Geo Information Top Cities per Country" does not work for Countries without "regions"
  • JLT-192571 - Server: java.lang.NullPointerException
  • JLT-190885 - fixed visit BT calculation for BTs using splittings from orphan web requests

Client

  • JLT-193823 - Dynamic Measure Matrix dashlet shows "LUMI [keyid...]" splittings on certain condition
  • JLT-192593 - Selecting the Query String in the "URI Pattern Value" measure doesn't toggle the "incl Query" button after adding the measure

JavaScript

  • ONE-8536 - Angular JS monitoring breaks our web app

Mobile

  • ONE-8767 - iOS Agent: Improved robustness of the internal database.
  • ONE-8874 - iOS Agent: DssClient improved symbol parser
  • ONE-6406 - Android Auto-Instrumentation: Updated Android build tools
  • ONE-7026 - Android Auto-Instrumentation: Updated Asmdex library
  • ONE-8699 - iOS Agent: Improved internal database error handling
  • ONE-8351 - iOS Agent: improved error handling in beacon url generator

JavaScript Agent

  • JLT-192350 - Web requests not correlated to actions after upgrade of Angular.js from 1.4.9. to 1.6.2
  • JLT-192956 - If a page is redirected due to a click on an element that overlaps a frame, the redirect action cannot be linked to the following load action.
  • JLT-193534 - Load actions originating from page redirects that take longer than 5 seconds to load might not be linked to previous page actions.

Mainframe

  • JLT-193549 - Memory leak in zRemoteAgent when IMS subagents are connected

Server

  • JLT-181761 - Upgrade VMWare Guest Lib to prevent spurious server crashes
  • JLT-193541 - Backend Process Memory Pressure When Calculating Memory Dump Keep Alive Sets
  • JLT-191607 - Test Automation: When tests executed with wrong category, Test Results dashlet wrongly displays all tests under the last test category.

PWH

  • JLT-190251 - Add possibility to change some column collations for SQLServer.

6.5.20.1009 Resolved Issues

55 (+ 1) critical issues, 760 (+ 22) total resolved issues

 Component change overview
ComponentTotalNew
.NET Agent100
Agent151
Client951
Collector490
Common20
Communication20
Core10
Correlation and Analysis310
DB Agent52
Dashboard10
Installer and Build20
Instrumentation10
Integration and Services10
Java Agent250
JavaScript10
JavaScript Agent11
Mainframe250
MessageBroker Agent50
Mobile410
Nginx11
PWH301
Plugins30
Runtime Diagnostics130
Server22810
Server Platform32
Session Storage10
UEM1063
WebUI370
Webserver Agent250

Most critical issues since the last public updates

JavaScript Agent

  • JLT-192322 - UEM option "Capture resource information" breaks customer's application
    • Impact: Can cause unexpected behavior on older IE browsers due to triggering the load event on images
    • Cause: setting instrumented third party images' src attribute to itself
    • Solution: remove this piece of code as it is no longer needed (if it ever actually was) in currently supported browsers

All resolved issues

Server Platform

  • JLT-188072 - OneAgent server/collector debug flags not handled correctly in ini file parser
  • JLT-179651 - Improved log for ArrayIndexOutOfBoundsException in CachingTimeSeries.

Server

  • JLT-190336 - Added improved and more detailed log messages for realtime analysis
  • 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-192169 - Improve logging capabilities for OneAgent connectivity
  • JLT-191306 - Null pointer check added to mitigate JVM crash.
  • JLT-187580 - Implement debug logging for one agent components
  • JLT-192240 - Enhance logging for confidential string serialization in order to debug permissions
  • JLT-192927 - License-Logfile dtactivation.txt doesn't contain correct expiry date for agent hour volumes.
  • JLT-191926 - Debug flag "com.dynatrace.diagnostics.ssl.protocols.unsafe" had no effect.
  • JLT-189404 - Incorrect log supression in MultiMessageBroadcaster

Nginx

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

PWH

  • JLT-189077 - Add possibility to skip validation of entered performance warehouse configuration data.

Client

  • JLT-192285 - Test execution's details displayed from a different execution on a Test Results dashlet chart

UEM

  • JLT-172631 - NullPointerException in ActionDefinitions.isKnownAction(..)
  • JLT-178000 - The MobileWorkload Dashlet should include web requests coming from mobile browsers.
  • JLT-192056 - Some regions were not resolving their region codes to a location

JavaScript Agent

  • JLT-192322 - UEM option "Capture resource information" breaks customer's application

Agent

  • JLT-192712 - ZDC Version check should only verify major/minor

DB Agent

  • JLT-191944 - Explain plan retrieval for SQL queries truncated by agent sensors displays more a specific error message for MySQL
  • JLT-167161 - Prevent from occasional java.lang.NullPointerException occuring in MariaDB JDBC driver

6.5.19.1013 Resolved Issues

54 (+ 4) critical issues, 738 (+ 23) total resolved issues

 Component change overview
ComponentTotalNew
.NET Agent101
Agent140
Client941
Collector491
Common20
Communication21
Core10
Correlation and Analysis310
DB Agent31
Dashboard10
Installer and Build20
Instrumentation11
Integration and Services10
Java Agent251
JavaScript11
Mainframe253
MessageBroker Agent50
Mobile410
PWH292
Plugins30
Runtime Diagnostics130
Server2186
Server Platform11
Session Storage11
UEM1032
WebUI370
Webserver Agent250

Most critical issues since the last public updates

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

.NET Agent

  • JLT-192329 - Instrumented .NET application crash "Common Language Runtime detected an invalid program."
    • Impact: .NET Agents with ADO.NET sensor that detect an MSSQL server cause the failure of the instrumented application
    • Cause: Agent instruments IL code to insert a return in a catch exception handler.
    • Solution: Do not add "return" code in such cases.

Mainframe

  • JLT-190358 -
    • 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.
  • JLT-180465 - Add the ability to set certain zLocalAgent debug flags
    • Impact: Must restart the zLocalAgent at minimum.
    • Cause: Certain diagnostic information is needed for effective issue resolution but not possible at this time. Also, existing diagnostic settings cannot be applied without restarting the zLocalAgent.
    • Solution: Add the ability to define new diagnostics settings and doing so without restarting the zLocalAgent.

All resolved issues

Server

  • JLT-189134 - Prevented server restart by fixing session synchronization bottleneck with large amount of sessions.
  • JLT-191887 - Potential NPE in ActionCenterCheck
  • 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-192366 - Server startup fails if system profile contains multiple measures with the same key
  • JLT-191700 - Reduce performance overhead for calcuation of the Failed Transaction and Failed User Action Count measures
  • JLT-190607 - Add additional log output in case measure reference is null

Instrumentation

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

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

Client

  • JLT-182851 - Clicking on Tier Contribution in the Baseline Details Dashlet no longer results in an empty Transaction Flow.

DB Agent

  • JLT-190253 - Oracle — explain plans not found due to whitespace trimming

PWH

  • JLT-186179 - Possibly server not starting due to Performance Warehouse connection issue.
  • JLT-185074 - Fixed version check of performance warehouse connect.

.NET Agent

  • JLT-192329 - Instrumented .NET application crash "Common Language Runtime detected an invalid program."

UEM

  • 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)

Java Agent

  • 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)

Mainframe

  • JLT-190358 -
  • JLT-180465 - Add the ability to set certain zLocalAgent debug flags
  • JLT-186354 - Handle the zdcVersion from the zDC, and log a message if it doesn't match.

Collector

  • JLT-191365 - Java 8 instrumentation may result in Illegal use of nonvirtual function call VerifyErrors

Server Platform

  • JLT-186982 - UnsupportedOperationException when ApplicationRequestResponseHandler is called for the Infrastructure system profile

Communication

  • JLT-189128 - Added log output for enabled TLS ciphers and protocols

Session Storage

  • JLT-190248 - Fix NPE on session analysis.

6.5.18.1011 Resolved Issues

50 (+ 1) critical issues, 715 (+ 22) total resolved issues

 Component change overview
ComponentTotalNew
.NET Agent91
Agent140
Client933
Collector481
Common20
Communication10
Core10
Correlation and Analysis310
DB Agent22
Dashboard11
Installer and Build20
Integration and Services10
Java Agent240
Mainframe220
MessageBroker Agent50
Mobile413
PWH271
Plugins31
Runtime Diagnostics130
Server2123
UEM1012
WebUI373
Webserver Agent251

Most critical issues since the last public updates

Webserver Agent

  • JLT-180660 - IIS crashes or corrupted HTML due to unwanted interactions between HTML injection and IIS user-mode output caching
    • Impact: In certain environments (depending on factors such as the specific customer app) that utilize IIS user-mode output caching, a delivery of a page with HTML injection would either lead to corrupted page contents or the w3wp process would crash.
    • Cause: IIS output caching functionality is sensitive to third-party modules making modifications to the cached response, especially its response headers.
    • Solution: A more conservative handling of response headers when caching gets detected.

All resolved issues

Client

  • JLT-190108 - Charts in incident chart dashlet are aggregated into a single chart despite chart splitting being enabled
  • 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

Collector

  • JLT-187076 - No more agent connections possible, "Unable to create connection for request ..." in log.

Server

  • JLT-178426 - Using concurrent map for selfmonitoring to prevent ConcurrentModificationException
  • JLT-189677 - Global incident downtimes do not activate correctly.
  • JLT-178235 - Potential keystore corruptions due to frequent unnecessary and non-atomic write access

UEM

  • JLT-190891 - Source actions are incorrectly reset during beforeunload if page load takes too long.
  • JLT-188390 - Using incremental responses with XHRs leads to readyState 3 events not always firing, thus information is received too late.

DB Agent

  • JLT-188091 - Database Agent Live View improved debug logging.
  • JLT-190762 - Improve DB Agent logging.

Mobile

  • ONE-7508 - iOS Agent: Improved action view name handling
  • ONE-8004 - iOS Agent memory leak during agent initialisation
  • ONE-7975 - iOS agent: webrequest to localhost was reported during first agent initialisation

Webserver Agent

  • JLT-180660 - IIS crashes or corrupted HTML due to unwanted interactions between HTML injection and IIS user-mode output caching

WebUI

  • JLT-189398 - Memory data does not get shown for HP-UX Java processes in the process details view of the WebUI.
  • JLT-160358 - Special characters are not shown correctly in the webdashboard breadcrumbs.
  • JLT-189698 - Bar chart bars aren't rendered correctly with high tile resolution on a small screen resolution.

PWH

  • JLT-189667 - An unexpected event during the system profile synchronization causes the performance warehouse to hang.

Plugins

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

.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

6.5.17.1012 Resolved Issues

49 (+ 1) critical issues, 693 (+ 23) total resolved issues

 Component change overview
ComponentTotalNew
.NET Agent81
Agent140
Client904
Collector472
Common20
Communication10
Core11
Correlation and Analysis310
Installer and Build20
Integration and Services11
Java Agent241
Mainframe220
MessageBroker Agent50
Mobile381
PWH262
Plugins20
Runtime Diagnostics130
Server2097
UEM991
WebUI341
Webserver Agent241

Most critical issues since the last public updates

.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.

All resolved issues

Client

  • JLT-189127 - Dashlet filter may not work correctly after renaming a business transaction
  • JLT-188619 - Prevent NullPointerException when opening TestAutomation dashlet migrated from previous AppMon version
  • JLT-189148 - Synthetic Monitoring: Disable 'Data feed' and remove configuration UI as desupported by Synthetic
  • JLT-189092 - Client UI slowdown when opening incident configuration with a very high number of condition measures.

Server

  • JLT-187542 - Log spam "Got subscription for dynamic measure with missing parent" after measure overload/explosion situation
  • JLT-189312 - Fixed very rare NPE in AbstractChartProcessor
  • JLT-167935 - Fix IllegalFormatConversionException in session storage debug log
  • JLT-189719 - Ensure that the bytecode of java proxy classes are not written to the classcache
  • JLT-189638 - Prevent NPE in scheduler in case of lost connection (log cosmetics)
  • JLT-189022 - Missing host health history or host availability status in the infrastructure overview
  • JLT-186249 - Changing the calculation of the "Application process unhealthy" incident to prevent false/positives and trigger more reliable

Webserver Agent

  • JLT-189109 - Introduce some speculative debug flags for the Employers support case

PWH

  • JLT-179843 - Two appmon server on one performance warehouse was possible.
  • JLT-188865 - Prevent unnecessary repetition of deletion step in aging task.

Core

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

Mobile

  • ONE-7414 - iOS Agent: Improved crash signal handling.

Collector

  • JLT-189087 - Prevent occasional null-pointer exception in scheduler when shutting down collector
  • JLT-180591 - Connection Pool Attachment not present when Exception happens on DB-Open (leads to <unknown> databases)

Integration and Services

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

UEM

  • JLT-189222 - Server: java.lang.StringIndexOutOfBoundsException StringIndexOutOfBoundsException occurred when performing action group processing if action name started with a left angle bracket

WebUI

  • JLT-189410 - Timeframe picker: WebUI blocks entering numbers into fields with french keyboard layouts

Java Agent

  • JLT-189425 - Added cassandra sensors early return in case of disabled bind value capturing

.NET Agent

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

6.5.16.1011 Resolved Issues

48 (+ 1) critical issues, 670 (+ 17) total resolved issues

 Component change overview
ComponentTotalNew
.NET Agent70
Agent140
Client861
Collector451
Common20
Communication10
Correlation and Analysis310
Installer and Build20
Java Agent230
Mainframe221
MessageBroker Agent51
Mobile372
PWH240
Plugins20
Runtime Diagnostics130
Server2026
UEM983
WebUI331
Webserver Agent231

Most critical issues since the last public updates

UEM

  • JLT-185339 - Secure session cookie option still sends cookie in non-secure browser requests.
    • Impact: Even though the UEM "Secure session cookie" option is enabled, the session cookie is still sent in a non-secure scenario.
    • Cause: The JavaScript Agent omits the W3C "Secure" cookie attribute when setting the "document.cookie" property.
    • Solution: When the UEM "Secure session cookie" option is enabled, the JavaScript Agent receives an internally-managed "ssc=1" option, and sets the W3C "Secure" attribute on the session cookie.

All resolved issues

MessageBroker Agent

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

UEM

  • JLT-185339 - Secure session cookie option still sends cookie in non-secure browser requests.
  • JLT-188392 - Where the mobile device name is not properly defined, the model Id is used for the device name.
  • JLT-174922 - Mobile beacon signal was not getting processed if it was not GZIPped

Server

  • JLT-187280 - Thread Dump on server stays in-progress until server restart in case monitors and/or threads change during Thread Dump creation.
  • JLT-188618 - Fix an Exception when reading path attachments from session-storage
  • JLT-187038 - During password change avoid log spam (exception stack traces) if invalid credentials were entered
  • JLT-171665 - Fix potentially inefficient requesting of pure-metadata which can lead to various problems, including unknown methods and corrupted purepaths.
  • JLT-185483 - Added debug flag to exclude one agents from GAT calculation
  • JLT-188433 - Adapted timeout for response times of asynchronous servlets

Webserver Agent

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

Mainframe

  • JLT-188429 - zRemoteAgent crash if the same IMS Control Region is hooked by two connected zDCs

Mobile

  • ONE-6300 - Android Auto-Instrumentation: Improved encoding of application id
  • ONE-7479 - iOS Agent: manual web request tagging not woking

WebUI

  • JLT-186572 - Limits for the number of tiles per dashboard and the splittings per tile is too low and cannot be changed.

Client

  • JLT-188301 - Transaction Flow shows wrong numbers for aggregated External Call Messaging nodes.

Collector

  • JLT-185186 - Modified query responsible for getting number of Oracle database cores for Database Agent.

6.5.15.1019 Resolved Issues

47 (+ 2) critical issues, 653 (+ 33) total resolved issues

 Component change overview
ComponentTotalNew
.NET Agent71
Agent141
Client854
Collector442
Common20
Communication10
Correlation and Analysis310
Installer and Build21
Java Agent230
Mainframe213
MessageBroker Agent41
Mobile351
PWH242
Plugins20
Runtime Diagnostics131
Server1968
UEM955
WebUI322
Webserver Agent221

Most critical issues since the last public updates

Agent

  • JLT-186560 - Nginx support for versions >= 1.11.10.
    • Impact: The Nginx agent crashes with Nginx versions >= 1.11.10.
    • Cause: The layout of an nginx internal structure changed.
    • Solution: The nginx agent accesses the changed structure via offsets. Manual offsets regeneration is required.

MessageBroker Agent

  • JLT-185337 - Avoid blocking call when checking internal instrumentation channel state, which may cause message broker transaction delay when reconnecting respective message broker agents.
    • Impact: Due to blocking time when uploading transformation information in a reconnect scenario may cause delay in message broker message flow transactions.
    • Cause: The check for instrumentation channel state was blocking without performing any transformation update.
    • Solution: Use non-blocking call when requesting instrumentation channel state.

All resolved issues

WebUI

  • JLT-187594 - The units "Auto" and "Occurrences" are visible in the charts.
  • JLT-186369 - Fix confidential strings for user action names. Now it is checked against Request URI from client-side confidential string type.

Client

  • JLT-186847 - Error rate display in database details dialog is wrong
  • JLT-184910 - Fixed an issue where the client unnecessarily reported an error after the refresh of the Host Health Dashboard.
  • JLT-159786 - Dialog "Monitored Business Transactions" might remove application splitting from Business Transaction
  • JLT-185465 - Wrong documentation link in Database Details and Live View dashlets

UEM

  • JLT-186650 - Perceived render time is not sent if a redirect is triggered during page load.
  • JLT-185625 - No sourceactions are created if there is a redirect during load
  • JLT-186551 - Programmatically triggered clicks in jQuery via jQuery.click() trigger creation of unexpected user actions.
  • JLT-187973 - Ajax request callbacks are not executed if jQuery.ajax is called with a jQuery version before 1.5.
  • JLT-186931 - Improve logging of failures during reading a visit.

.NET Agent

  • JLT-185159 - Fix potential problems related to .NET Thread dumps

Agent

  • JLT-186560 - Nginx support for versions >= 1.11.10.

Collector

  • JLT-188090 - Additional debug properties to fine-tune connection timeouts.
  • JLT-183106 - Fix a potential NullPointerException on collector during reconnect to server.

PWH

  • JLT-186230 - Added debug flags to configure percentiles retention time and clean-up parameters.
  • JLT-188608 - Fix a performance warehouse percentiles cleanup bug.

Server

  • JLT-187039 - Empty splitting value causes NPE in Realtime Business Transactions Feed.
  • JLT-186819 - Fix occasional null pointer exception when removing a schedule while no connection to collector
  • JLT-187531 - Fix a potential BufferUnderflow exception while reading incidents from sessions.
  • JLT-183700 - Potential log spam during session synchronization with disk in case of missing IO permissions.
  • JLT-177065 - Plugin-based measures are not be correctly created when generating a system profile from a system profile template.
  • JLT-184363 - Potential null pointer exception due to IO error during session restoration on server startup
  • JLT-187125 - Start date of recurring downtimes is not respected by the scheduler
  • JLT-188614 - Fix potential performance issue introduced with 6.5.14

Mobile

  • ONE-6905 - Android Auto-Instrumentation: Improved Java version parsing (for Windows)

MessageBroker Agent

  • JLT-185337 - Avoid blocking call when checking internal instrumentation channel state, which may cause message broker transaction delay when reconnecting respective message broker agents.

Installer and Build

  • JLT-187955 - Update to new code signing certificate and to digest hash algorithm SHA-256

Webserver Agent

  • JLT-187043 - Introducing troubleshooting debug flags debugDisableApacheHookCreateRequest, debugDisableApacheHookPostReadRequest, debugDisableApacheHookFixups, debugDisableApacheHookHandler, debugDisableApacheHookLogTransaction, debugDisableApacheModifyEtagFilter, debugDisableApacheCaptureHeadersFilter, debugDisableApacheReadPostParameterFilter and debugDisableApacheInjectionFilter for analyzing Apache agent related problems.

Runtime Diagnostics

  • JLT-169257 - Added debug logging for BT analyzers

Mainframe

  • JLT-186490 - The ZLocalAgent (zdc) is connected to a zRemoteAgent, but the zDC was never initialized, so no CICS agent register.
  • JLT-188228 - zRemoteAgent deadlock when the zLocalAgent (LPAR) takes a severe hit, such as a check stop
  • JLT-187606 - Reduce logging level for the zLocalAgent-zRemoteAgent reconnect attempt messages

6.5.14.1012 Resolved Issues

45 (+ 1) critical issues, 620 (+ 26) total resolved issues

 Component change overview
ComponentTotalNew
.NET Agent61
Agent131
Client814
Collector424
Common20
Communication10
Correlation and Analysis310
Installer and Build10
Java Agent230
Mainframe181
MessageBroker Agent30
Mobile340
PWH221
Plugins21
Runtime Diagnostics121
Server1888
UEM904
WebUI300
Webserver Agent210

Most critical issues since the last public updates

Agent

  • JLT-178666 - PHP Agent introduces around 30% overhead at a magento store.
    • Impact: Agent overhead and application slow down in response time
    • Cause: Copying data buffers instead of sharing beetween PHP and Agent
    • Solution: Optimisations in AutoSensors and data handling routines

All resolved issues

Server

  • JLT-186357 - Fix failure during export of purepaths from a just stored session.
  • JLT-185252 - Confidential strings feature doesnt mask the exception message in the Method column, but it does that in the Argument column
  • JLT-186132 - Copy Template Agent Group to existing System Profile is not copying the sensor placement
  • JLT-176125 - NullPointerException in OneAgent mobile message processing when agent is not registered anymore
  • JLT-185706 - NullPointerException after a "JVM Stuck" incident couldn't be created
  • JLT-186351 - Process Availability Violation incident does not trigger actions
  • JLT-185467 - Configurations migrated to/via 6.2 sometimes won't send notifications for infrastructure alerts
  • JLT-175961 - Occasional NPE and/or IOOBE when trying to read from session file while shutting down server

Runtime Diagnostics

  • JLT-185701 - Fix a potential NullpointerException when creating default measures for database nodes.

Client

  • JLT-186313 - Fixed an issue with the Worldmap's Nightmode
  • JLT-173993 - DB Agent: Looking up execution plans not possible in PurePath and Database dashlets for RAC environments.
  • JLT-186296 - Dynamic Measure Matrix shows different names for same measures
  • JLT-186817 - Context menu on System Profiles broken in Incidents dashlet.

Collector

  • JLT-185696 - Logging improvements for oneagent connection data
  • JLT-185357 - DB agent permissions read from per-profile configuration (wrong) vs from the global role only (expected)
  • JLT-186162 - Fixed VerifyError in lambda generated classes.
  • JLT-183739 - Add support for client side of Spring Webservices

UEM

  • JLT-184278 - If during a redirect a frame on the following page is loaded earlier than the JS Agent on the parent frame, source action information is lost.
  • JLT-179886 - Detected application sometimes not correctly propagated from server-side PurePath to user action.
  • JLT-183158 - Two NullPointerExceptions when modifying the Visits > Conversion Count measure.
  • JLT-177332 - If timed action support module is enabled, calls to setTimeout from within object context lose fallback to global context if called with evaluating code.

Agent

  • JLT-178666 - PHP Agent introduces around 30% overhead at a magento store.

PWH

  • JLT-185617 - Added debug flags to incident rule cache.

Plugins

  • JLT-185732 - (separate download) Server timeline plugin: Report is empty when the dashlet has no splittings

Mainframe

  • JLT-183178 - Better zLocalAgent-zRemoteAgent reconnection attempt handling to prevent zDC shutdown.

.NET Agent

  • JLT-183213 - Crash of Universal App on Windows 8 because of incorrect Drive-Enumeration-Handling

6.5.13.1014 Resolved Issues

44 (+ 5) critical issues, 594 (+ 38) total resolved issues

 Component change overview
ComponentTotalNew
Client775
Collector381
Communication10
DotNETAgent51
InstallerAndBuild10
JavaAgent236
MainframeAgent171
MessageBrokerAgent30
Mobile311
NGINXAgent50
OneAgent60
PHPAgent41
PWH214
Plugins10
Server1817
ServerCorrelation310
ServerRTA111
UEM865
WebUI303
WebserverAgent222

Most critical issues since the last public updates

MainframeAgent

  • JLT-184157 - zRemoteAgent crash at subagent INITialization time.
    • Impact: zRemoteAgent crashed.
    • Cause: The zRemoteAgent received the license update in the controller stream thread and tried to process registration events there. This caused a memory contention issue with the event processing thread.
    • Solution: Remove the registration of the events from the controller thread. Register them immediately after the INIT event is received from the subagent.

WebserverAgent

  • JLT-178724 - SubAgents were not discovered/reconnected after WebserverAgent reconnect.
    • Impact: Any paths from not recovered SubAgents were dropped from that time on.
    • Cause: SubAgent registration events were dropped due to a full event sender queue.
    • Solution: Agent checks periodically for non-registered SubAgents and resend the registration event if necessary.
  • JLT-185144 - Introduce debug flag "debugiissuppresspecialrequestresponseflushnative" to avoid flushing the special request response immediately as this allegedly causes memory corruption.
    • Impact: Due to corrupted memory the w3wp crashes.
    • Cause: A call to IHttpResonse::Flush seems to cause memory corruption in certain situations.
    • Solution: Introduce debug flat "debugiissuppresspecialrequestresponseflushnative" to disable flushing and check if this solves the problem.

PHPAgent

  • JLT-184622 - PHP agent PHP Logging sensor does not instrument logging functions for new release of Zend Framework engine
    • Impact: PHP Logging sensor does not instrument related functions
    • Cause: The problem is caused by the architecture change in a new release of Zend Framework
    • Solution: Added new file structure to PHP Logging sensor

UEM

  • JLT-184537 - NullPointerException in ServletRequestWrapperUtils.getUrlForAppDetection().
    • Impact: NullPointerException.
    • Cause: Instrumented servlet returns null on getUrl().
    • Solution: null check.

All resolved issues

JavaAgent

  • JLT-181568 - Excluded Groovy classes from instrumentation.
  • JLT-146567 - PMI measure aquisition not working for some WebSphere rare configurations.
  • JLT-181789 - Add support for JBoss Logmanager 1.5.4
  • JLT-184856 - java.lang.NoSuchFieldError: dt_CursorId when using MongoDB Java Driver 3.4.x
  • JLT-184389 - Introducing a java agent option to turn of trimming of SQL statements for the JDBC sensor
  • JLT-177618 - Detect Java 9 and disable Agent.

Server

  • JLT-185060 - No more data is collected for dynamic JMX measures after the corresponding JMX config measure is changed.
  • JLT-184403 - Log progress of reading sessions in server startup.
  • JLT-179169 - Incidents: Comparison method violates its general contract
  • JLT-179751 - License may lock if a server has multiple PTR-records in DNS
  • JLT-184809 - NullPointerException in CollectorCenter
  • JLT-184359 - Log spam due to incorrect certificate configuration
  • JLT-183201 - Deadlock on Server

PWH

  • JLT-184921 - Previously failed performance warehouse migrations are not detected during connect.
  • JLT-184650 - Fix percentile data import when using different systemprofile names.
  • JLT-184120 - Fixed some bugs of performance warehouse systemprofile import.
  • JLT-173953 - Avoid nullpointer exception after performance warehouse schema rebuild.

WebUI

  • JLT-185123 - Drill down into South Sudan is impossible on the World map.
  • JLT-182850 - In some cases the world map could crash if region data is not available.
  • JLT-184623 - For some countries the drill down from World map to User analytics does not show any data.

Collector

  • JLT-179847 - Added debug flag for VerifyError on Oracle 1.8 VMs.

MainframeAgent

  • JLT-184157 - zRemoteAgent crash at subagent INITialization time.

Client

  • JLT-165874 - Nullpointer exception in performance warehouse configuration dialog.
  • JLT-184640 - IndexOutOfBoundsException when creating measure with chinese language pack
  • JLT-183123 - Client that is started in kiosk mode may end up in restart loop if it is connected to multiple servers with different versions
  • JLT-184787 - NullPointerException when checking for required restart during collector configuration
  • JLT-172313 - Issue with selecting a category or resource type in the edit dialog of the W3C Resource Timing measure

UEM

  • JLT-182152 - Fixed division by 0 during 3rd party measurement evaluation.
  • JLT-184683 - If a page forces a redirect via meta tag, the JS Agent is not capable of creating linked actions.
  • JLT-185089 - If called without arguments, XHR actions that are created via jQuery.ajax() cannot be closed and time out.
  • JLT-184807 - Fix NullPointerException during reading visit from session storage.
  • JLT-184537 - NullPointerException in ServletRequestWrapperUtils.getUrlForAppDetection().

WebserverAgent

  • JLT-178724 - SubAgents were not discovered/reconnected after WebserverAgent reconnect.
  • JLT-185144 - Introduce debug flag "debugiissuppresspecialrequestresponseflushnative" to avoid flushing the special request response immediately as this allegedly causes memory corruption.

Mobile

  • JLT-184639 - iOS Agent: crash reports sent with invalid timestamp and discarded on server if mobile agent timesync failed

PHPAgent

  • JLT-184622 - PHP agent PHP Logging sensor does not instrument logging functions for new release of Zend Framework engine

ServerRTA

  • JLT-184876 - Visit store aging timer task will be started delayed to avoid NullPointerException when measure auto subscription is turned on.

DotNETAgent

  • JLT-184366 - Preventing .NET agent from sending empty method names in a Thread Dump

6.5.12.1015 Resolved Issues

39 (+ 3) critical issues, 556 (+ 47) total resolved issues

 Component change overview
ComponentTotalNew
Client727
Collector372
Communication10
DotNETAgent41
InstallerAndBuild10
JavaAgent172
MainframeAgent161
MessageBrokerAgent32
Mobile306
NGINXAgent50
OneAgent60
PHPAgent30
PWH170
Plugins11
Server17412
ServerCorrelation311
ServerRTA102
UEM816
WebUI274
WebserverAgent200

Most critical issues since the last public updates

UEM

  • JLT-173792 - Monitored Webservers: Vulnerability in UEM session cookie (dtCookie) using CRLF injection attack.
    • Impact: A forged request allows to add arbitrary response headers sent to the same client from which the request originated. The cookie is not stored, this response is never sent to other users. This vulnerability is an attack vector for further attacks such as Cross-User Defacement, Cross-Site Scripting, Page Hijacking if the attacker wants to attack the client which sends the request. Possible Cache Poisoning attack where the attacker sends the request directly which may impact the other users of the same cache (i.e. proxy).
    • Cause: Missing validation of cookie value.
    • Solution: Added validation of cookie value.

DotNETAgent

  • JLT-182580 - The agent might crash with a System.NullReferenceException when the collector sends updates for the UEM configuration and the UEM configuration update state is inconsistent.
    • Impact: Instrumented application crashes when collector sends updates for the UEM configuration to the agent.
    • Cause: A missing null check for an inconsistent UEM configuration state.
    • Solution: Added null check to avoid possible System.NullReferenceException.

Client

  • JLT-174592 - Database Agent: Database Live View (Database Health) dashlets are shown with no data when agent not available
    • Impact: Client shows empty dashlets and logs NullPointerException
    • Cause: System calls hashCode method calculated over fields containing nulls
    • Solution: Disables links to depended dashlets when agent not available

WebUI

  • JLT-178112 - Chart does not contain all series for selected splittings.
    • Impact: In some cases the user did not see certain series although the corresponding splittings were selected and the series contain data.
    • Cause: Series without data affected the max series limit calculation.
    • Solution: In the max series calculation only series with data are considered.

All resolved issues

UEM

  • JLT-181576 - Wrapped two mobile correlation log messages around the com.dynatrace.diagnostics.debugMobileCorrelation debug flag to prevent log spam.
  • JLT-182291 - Performing a filter in the Visits Dashlet, that included a regular expression with escape characters, failed to return the correct results.
  • JLT-182606 - If JavaScript agent is requested via REST, the configured cookie domain setting is ignored.
  • JLT-161539 - Modifications to the mobile correlation, to cater for timings from the mobile agent, that have been adjusted to account for the server time.
  • JLT-178986 - URL for application detection can get malformed for webMethods.

Client

  • JLT-182907 - Open in client link not working when using non standard port for client to server connections
  • JLT-183732 - Failed transaction percentage measure not correctly drilling down to filtered purepath, instead shows all
  • JLT-183173 - Client crashes when a dashboard containing a dual axis chart with a timeframe offset gets too small.
  • JLT-182747 - Report of dual axis chart would fail, when a visible measure had no data.
  • JLT-174592 - Database Agent: Database Live View (Database Health) dashlets are shown with no data when agent not available
  • JLT-182575 - User not able to change sensor properties on Mac OS X.
  • JLT-183906 - Fixed drilldown from ApplicationOverview's UEM item to the visits dashlet

Mobile

  • ONE-6141 - iOS Agent: Improved mobile tag transport encoding
  • ONE-6230 - Android Agent: added content-type header to server post requests.
  • ONE-6229 - iOS Agent: added content-type header to server post requests.
  • ONE-2591 - Android Auto-Instrumentation: improved detection of HttpURLConnection web requests
  • ONE-6112 - Android Auto-Instrumentation: Improved support for non-standard conform HttpURLConnection usage
  • ONE-6142 - Android Agent: Correctly handle underscores in ApplicationID

Collector

  • JLT-173181 - Current server session is closed on collector because collector watchdog is not notified while waiting for send buffer.
  • JLT-183424 - Failing DBAgent start on adding one to config reported twice, including with NPE

MessageBrokerAgent

  • JLT-182646 - A new (WSMB) agent option with name optionPropagateNodesFilterWSMBNative was introduced filtering all message flow propagate message nodes (stage 2), that are not responsible for starting paths, inclusive their respective node completion nodes (stage 4) via given globbing patterns on the respective propagate node names.
  • JLT-182645 - A new (WSMB) agent debug flag with name debugDisablePropagateNodesMonitoringWSMBNative was introduced filtering all message flow propagate message nodes, that are not responsible for starting paths, inclusive their respective node completion nodes.

Server

  • JLT-178859 - License UEM reservations for autodetected applications were falsely possible.
  • JLT-180558 - Occasional IllegalArgumentException when sorting tree of AgentOverview portlet for reporting because comparison method violates its general contract
  • JLT-181547 - Server fails to start since "Repository Aging Task" is configured on system profile
  • JLT-181941 - Prevent adding values of host performance measures which are invalid
  • JLT-182036 - Slow REST response when accessing alert via UUID due to unnecessary data being queried from performance warehouse
  • JLT-181554 - Open incidents of rules not marked "Store in Performance Warehouse" were duplicated when saving system profile.
  • JLT-183006 - Mobile Workload Dashlet Displays Insufficient Permissions for User with Administrative Rights
  • JLT-180286 - Database Agents are no longer listed as hosts in Infrastructure Dashlet.
  • JLT-184188 - Fix a deadlock during session-storage management on backend server.
  • JLT-177765 - Improved debug logging for charting issues.
  • JLT-182994 - Self-monitoring Collector binds wrong agent listen port if '-listen' argument is passed to dtserver process)
  • JLT-179109 - Changes to baseline violation detection settings don't get applied till next server restart

JavaAgent

  • JLT-182957 - Logging sensor with empty severity doesn't work as exepcted
  • JLT-184110 - Prevent agent log spam for Glassfish webservice sensor

MainframeAgent

  • JLT-183677 - Message counts for the zRemoteAgent will roll over after 2g. Should be 64 bit counters.

Plugins

  • JLT-170398 - (Not in update, separate download) Shipped metadata of SNMP trap did not correspond to actually sent data.

DotNETAgent

  • JLT-182580 - The agent might crash with a System.NullReferenceException when the collector sends updates for the UEM configuration and the UEM configuration update state is inconsistent.

ServerCorrelation

  • JLT-180279 - CorrelationNG: fix high CPU usage when transactions with a very high number of subpaths completes.

WebUI

  • JLT-181589 - On WebUI dasboards, alert tiles were displayed without status icons in Internet Explorer 11 and Edge.
  • JLT-163768 - For some relative timeframes the displayed auto resolution did not match the actual requested one.
  • JLT-183416 - World map does not show visits for Hong Kong.
  • JLT-178112 - Chart does not contain all series for selected splittings.

ServerRTA

  • JLT-170558 - Occasional IndexOutOfBoundsException in BaselineChartingMeasurementAggregator
  • JLT-163215 - Occasional NPE after trying to chart from a closed session file

6.5.11.1012 Resolved Issues

36 (+ 1) critical issues, 509 (+ 24) total resolved issues

 Component change overview
ComponentTotalNew
Client651
Collector352
Communication10
DotNETAgent30
InstallerAndBuild10
JavaAgent150
MainframeAgent151
MessageBrokerAgent10
Mobile244
NGINXAgent50
OneAgent60
PHPAgent30
PWH173
Server1628
ServerCorrelation301
ServerRTA82
UEM751
WebUI230
WebserverAgent201

Most critical issues since the last public updates

Server

  • JLT-178136 - Memory problems on server when using NGINX one agents
    • Impact: - Memory problems on the server - Webrequest response time missing for PurePaths using a webserver one agent
    • Cause: Wrong api created for webserver one agents causes PurePaths to remain processing for 10min
    • Solution: Corrected api. Increased CorrelationEngine robustness for such situations. Adapted default timeout for waiting on async webrequest response times.

All resolved issues

PWH

  • JLT-167974 - Only one hour of charting data available when appmon server was started the first time after upgrade.
  • JLT-181526 - Cleanup task may delete open incidents from performance warehouse.
  • JLT-180774 - Introduce debug flag to restrict performance warehouse incident retention time.

ServerCorrelation

  • JLT-176327 - Add more checks and logging regarding custom tagging and UEM tagging to find a performance bottleneck.

WebserverAgent

  • ONE-5930 - Time provider logging never showed up in master agent logs

Server

  • JLT-181142 - Increased server restart time due to self-monitoring Collector
  • JLT-173387 - DssService does not always delete temporary files
  • JLT-171070 - Prevent the creation of system profile names with trailing space characters or special characters via REST interface
  • JLT-180570 - Unique agent names with index feature frees index after soft restart of Apache webserver even though it is sill in use, leading to duplicate agent names
  • JLT-180253 - Exec Time metric based measures are not booked correctly
  • JLT-181144 - Prevent unnecssary writes to the ini files
  • JLT-180355 - Wildcard '*' is not applied in ignore mount point rule in infrastructure
  • JLT-178136 - Memory problems on server when using NGINX one agents

Mobile

  • JLT-180108 - iOS Agent: Improved compatibility with LP-Messaging
  • JLT-180814 - iOS Agent: Improved handling of local URLs
  • ONE-5979 - Android Agent: wrong timing for POST web requests using HttpURLConnection framework
  • ONE-5974 - Android Auto-Instrumentation: Missing lifecycle instrumentation if activity class hierarchy was distributed over multiple dex files

Collector

  • JLT-169129 - DB Agent: improved error logging on connection attempt.
  • JLT-165230 - Db Agent: improved logging on shutting down obsolete agents.

ServerRTA

  • JLT-180091 - Fix NullPointerException caused by race condition.
  • JLT-163216 - In realtime analysis check and log entry added to avoid NullPointerException

Client

  • JLT-179170 - Sanity check in EntryScreen

MainframeAgent

  • JLT-180385 - Add debugPingNative logging support to the zLocalAgent

UEM

  • JLT-181506 - The mobile tag was not processed correctly if the application id contained an underscore.

6.5.10.1012 Resolved Issues

35 (+ 2) critical issues, 485 (+ 39) total resolved issues

 Component change overview
ComponentTotalNew
Client643
Collector335
Communication10
DotNETAgent31
InstallerAndBuild10
JavaAgent150
MainframeAgent140
MessageBrokerAgent10
Mobile202
NGINXAgent50
OneAgent60
PHPAgent30
PWH142
Server15410
ServerCorrelation294
ServerRTA60
UEM7410
WebUI230
WebserverAgent192

Most critical issues since the last public updates

Client

  • JLT-169266 - Saving DB Agent configs shouldn't throw NullPointerException.
    • Impact: NPE reported in client logs. Also saving DB Agent configs could fail silently.
    • Cause: Default value when creating request wasn't provided so in case of some communication problems or internal exceptions, saving DB Agents config may throw NPE, because so null had to be casted to boolean. Also, in case the saving fails for any reason, it wouldn't be reported.
    • Solution: Provided default value in case the request fails (Boolean.FALSE). Added SEVERE log entry when saving configs fails.

Server

  • JLT-178555 - In extremely rare cases storing a profile containing specific garbage collection measures, or processing measurememnts for specific garbage collection measures causes a NPE.
    • Impact: Referring to metric id of null metric reference during RTA processing causes permanent NPEs.
    • Cause: Configuration inconsistencies in rare cases cause metric reference of specific garbage collection measures to be null during RTA processing.
    • Solution: Changed RTA processing to fetch metrid id directly and not via metric reference.

All resolved issues

UEM

  • JLT-174352 - Added missing documentation and provided links for 'Map detected domains' and 'Resource Summary Configuration' dialogs
  • JLT-178943 - NullPointerException in WorldMap when server is connected
  • JLT-179196 - fixed NPE in application drop-down in UEM settings
  • JLT-178945 - Fixed null-check in EndUserRootPath
  • JLT-175976 - Drill down to the User Action PurePaths, from the User Action table in the Visits Dashlet, returned an empty table. This occurred when the Visits Dashlet was viewed from a drill down of completed visits from World Map.
  • JLT-178799 - Prevent mobile application detection for mobile apps called 'Default Application'
  • JLT-178358 - PureLytics Stream fields serverErrors and clientErrors not filled with data.
  • JLT-178752 - If an XHR happens during beforeunload, pagehide or unload, source actions cannot be linked to subsequent load actions.
  • JLT-179099 - Improved logging of measurementCollection with com.dynatrace.diagnostics.rta.debugMeasureCollection.
  • JLT-179082 - Source action cookie can get very long, depending on URL length. Added feature to disable subdomain source action support to store data in session storage instead of cookie.

Mobile

  • ONE-5627 - Android Agent: prevents reporting of invalid battery level
  • ONE-5625 - Android Auto-Instrumentator: improved url verification for encoded urls

DotNETAgent

  • JLT-178904 - Iterating over assembly references via reflection led to an exception, if ADK is used.

Collector

  • JLT-179029 - Broken reconnect of 6.1 agent when connecting to 6.3 collector and later
  • JLT-170534 - DB Agent: Don't log stacktraces for problems that don't need it.
  • JLT-178279 - T3 stitching not working with Weblogic 12.2.1.2.0
  • JLT-178418 - Full stacktrace shouldn't be included when logging SQL problems when verifying DB Agent connection status.
  • JLT-178885 - Improve logging if Agent connection can't be established due to synchronization problem.

WebserverAgent

  • JLT-176313 - Web request is not correlated to user action after rewrite, because Apache Agent injects the JS agent with the wrong request and response ID.
  • JLT-177636 - Apache agent reports wrong "max threads" values.

Server

  • JLT-171100 - Ensure that actual exception stack trace is still in log even though log is spammed with error messages without stack trace (i.e., OmitStackTraceInFastThrow is on)
  • JLT-178985 - ConcurrentModificationException when writing incidents into the performance warehouse
  • JLT-164742 - Self-monitoring Collector might not be able to connect to AppMon Server if custom Collector connection settings are used
  • JLT-180086 - Fix a potential NullPointerException when transferring InheritanceMap data during cpu-sampling.
  • JLT-173967 - Fix a potential ConcurrentModificationException in the loaded classes on collector.
  • JLT-178555 - In extremely rare cases storing a profile containing specific garbage collection measures, or processing measurememnts for specific garbage collection measures causes a NPE.
  • JLT-179553 - PurePath name might be wrong when CorrelationNG and OneAgent are used
  • JLT-178970 - Application Detection failed to match in some circumstances, resulting in "Default Application" where a configured application should have been detected.
  • JLT-179185 - When creating a report from a Dashboard the filter is appended in the export even if "Append Filter" is unchecked.
  • JLT-168843 - Re-analyzing a session file twice produces wrong measurements

ServerCorrelation

  • JLT-178501 - CorrelationNG: fix calculation of synchronization and wait times of OneAgent paths.
  • JLT-180150 - Memory management for sub-path correlation engine completed buffer not working correctly because available weight of transactions is increased twice.
  • JLT-148746 - Application name is not set on timed-out pure-paths because application name is set on exit event which is not received in case of time-out.
  • JLT-178971 - CorrelationNG: fix race condition when propagating APIs from a serverside purepath to a useraction purepath.

Client

  • JLT-169266 - Saving DB Agent configs shouldn't throw NullPointerException.
  • JLT-162000 - Improved logging for case when collector is not found when configuring DB Agent.
  • JLT-178940 - Added null pointer check to avoid exception during checking of dependent rate measures when deleting a transaction result measure.

PWH

  • JLT-177276 - Server stops writing measurements to performance warehouse if a data integrity exception happens.
  • JLT-178927 - Performance Warehouse: Introduce adjustable incident synchronisation time frame.

6.5.9.1501 Resolved Issues

33 (+ 3) critical issues, 446 (+ 40) total resolved issues

 Component change overview
ComponentTotalNew
Client615
Collector282
Communication10
DotNETAgent21
InstallerAndBuild10
JavaAgent151
MainframeAgent140
MessageBrokerAgent10
Mobile182
NGINXAgent50
OneAgent60
PHPAgent31
PWH123
Server14413
ServerCorrelation252
ServerRTA60
UEM649
WebUI230
WebserverAgent171

Most critical issues since the last public updates

Server

  • JLT-177072 - Host health incidents are always sent, even at configured downtimes
    • Impact: Incident downtimes have no effect on host health incidents, they are always fired
    • Cause: Host health incidents are fired for the Infrastructure system profile, but there is no incident rule engine to disable for this profile
    • Solution: An incident rule engine is also created for the Infrastructure system profile so that incident rules can be disabled for this system profile. Note that host health incidents can only be suppressed globally via incident downtimes of the Infrastructure system profile or global downtimes, downtimes on other system profiles will have no effect.
  • JLT-177326 - Processing CI data for removed measures causes failures.
    • Impact: Continuous Integration PurePath processing and data aggregation might fail.
    • Cause: Looking up for a missing measure in cache.
    • Solution: Ommit Continuous Integration data processing in case a measure couldn't be located in cache.

UEM

  • JLT-177131 - AngularJs de-support success and error callback methods
    • Impact: XHRS throw errors on the page when Angular >= 1.6 is loaded with the Angular sensor enabled
    • Cause: The sensor invokes the success and error callback methods to ensure actions are created. In 1.6 these are desupported.
    • Solution: Use safer 'then' function to handle both success and error functions if they exist and support 'catch'. Adds additional safety conditionals

All resolved issues

UEM

  • JLT-178362 - Fix creation/update of visits and avoid incomplete visits due to concurrent VisitStore access
  • JLT-176370 - After creating a Web Request Response Time measure and restarting the server, the measure was missing from the metrics list.
  • JLT-175153 - User Action Purepaths have weird names on IE8 and IE9 if a < sign is used for the remove special characters setting.
  • JLT-175978 - Make sure Default Application is never updated with AutoDetectType other than none.
  • JLT-178271 - SEVERE log spam of PureLytics Stream
  • JLT-177131 - AngularJs de-support success and error callback methods
  • JLT-174816 - Child load actions defines application for parent action.
  • JLT-164930 - Adapt injection behavior if request is forwarded in servlet container and URL is rewritten
  • JLT-169334 - Improved logging of visit conversion with com.dynatrace.diagnostics.visit.debugVisitConversionFilter and com.dynatrace.diagnostics.visit.debugVisitConversionSampling

Server

  • JLT-175684 - Database dashlet seems to be misrepresenting data from the configured timeframe
  • JLT-172415 - Logfile pollution caused by NullPointerException in UemSignalMessageProcessor
  • JLT-154895 - Host health states are sometimes shown as offline when monitored processes are configured
  • JLT-173519 - Improve logging in case of problems with deleting sessions from storage.
  • JLT-177072 - Host health incidents are always sent, even at configured downtimes
  • JLT-178317 - dtcmd (separate download): listing agents fails in case eventcount, skippedevents, skippedpurepaths or totalPurePathCount counters have values above 2^31-1.
  • JLT-177499 - Switch cont. recording sessions also when a configurable recording time (default 4h) is reached.
  • JLT-173373 - Prevent possible log spam (NPE) while agent registration and server is under high load
  • JLT-176157 - Fix server stops recording (manual) with full storage queue, nothing written to manual recording session.
  • JLT-177326 - Processing CI data for removed measures causes failures.
  • JLT-176183 - Problems post-processing memory-dumps on analysis-server as the available diskspace is out of sync
  • JLT-169166 - (Change reverted)
  • JLT-177329 - Sending report emails with StartTLS does not work if the SMTP server is configured to REQUIRE StartTLS

Client

  • JLT-171588 - Drilldowns from BT Details might have resulted in an empty dashlet.
  • JLT-177251 - Filter for drilldown from incidents to PurePaths has wrong timeframe when incident evaluation timeframe is > 10s.
  • JLT-168322 - DB Agent: Getting explain plan for queries with whitespaces leads to message "The db did not return any explain plan for the query. It is possibly no longer cached"
  • JLT-177463 - In rate cases, refreshing task records causes a null pointer access on the client.
  • JLT-177013 - Fixed an issue where Business Transaction Hotspots could not be opened via the cockpit

ServerCorrelation

  • JLT-177957 - CorrelationNG: possible Backendserver crash after severe memory problems with UEM enabled.
  • JLT-177288 - CorrelationNG: fix race condition when propagating the application name to the User action PurePath.

DotNETAgent

  • JLT-174359 - Fix a problem with Sampling causing huge object churn. This lead to higher memory usage on Server Applications.

Mobile

  • JLT-177140 - DTXDssClient: Improved relative path handling for dSYM files
  • JLT-177292 - Android agent: Introduced a flag (DTXAllowFileCookies) which enables file cookies support for Hybrid applications.

PWH

  • JLT-175477 - Session export/charting fails because of too high value in database.
  • JLT-178141 - Insertion of incidents into performance warehouse fails if incident desciption or message is too long.
  • JLT-175821 - Performance Warehouse connect/reconnect task hangs if synchronize of system profile fails.

Collector

  • JLT-177482 - Only the default user's database (tablespace) is enlisted instead of all tablespaces hosted on dbServer.
  • JLT-172311 - User Plugin logging may be impacted by malformed log messages.

WebserverAgent

  • JLT-178500 - HTML truncation due to gzip buffer exhaustion on certain long compressed HTML pages.

JavaAgent

  • JLT-175779 - Agent disconnects result in CICS Transaction Gateway processes consuming Java Agent licenses

PHPAgent

  • JLT-174027 - PHP Agent: added debug option to enable log of Connection Pool Event fulfillment

6.5.8.1013 Resolved Issues

30 (+ 2) critical issues, 406 (+ 40) total resolved issues

 Component change overview
ComponentTotalNew
Client568
Collector262
Communication10
DotNETAgent10
InstallerAndBuild10
JavaAgent140
MainframeAgent142
MessageBrokerAgent10
Mobile161
NGINXAgent50
OneAgent62
PHPAgent20
PWH90
Server13112
ServerCorrelation237
ServerRTA60
UEM550
WebUI231
WebserverAgent165

Most critical issues since the last public updates

Collector

  • JLT-175909 - .NET Agent: Delayed monitored application startup caused by log spam inside Collector.
    • Impact: Delayed monitored application startup or application is not monitored.
    • Cause: Missing inheritance map entries for .NET classes.
    • Solution: Throttle logging inside Collector for missing entries inside inheritance map.

OneAgent

  • ONE-5045 - Nginx OneAgent causes worker processes to hang when injecting into large gzipped HTML pages.
    • Impact: Some requests to large HTML pages never finish.
    • Cause: The agent does not correctly release data buffers used for HTML injection.
    • Solution: Fixed the way the agent handles Nginx's internal data buffers when recompressing data after injection.

All resolved issues

Client

  • JLT-173073 - Agent group settings of inactive system profile configuration may be pasted
  • JLT-175834 - Older servers may cause an error in Start Center: There was an error checking the servers certificate and key pair: chain is null/empty or keystore error.
  • JLT-175503 - Transaction Flow expansion and record limit improvement
  • JLT-176232 - Fixed an issue in the Host Overview Dashboard addressing an update issue when the host agent selection has been changed
  • JLT-175965 - NPE in System Information Dashlet
  • JLT-170704 - Client connections tunneled sometimes caused configuration issues when using multiple servers.
  • JLT-160338 - Host Details can handle more than 300 processes now
  • JLT-172947 - Adding Count measure to Chart may add wrong measure if a BT has multiple result measures

Server

  • JLT-170005 - Load balancing task failed to calculate average load for masterAgents properly in certain cases.
  • JLT-172297 - Fix a potential problem that led to exceeding the max entry-size of sessions files while updating visits in session-storage.
  • JLT-175231 - Occasionally custom tagged Paths didn't get stored due to a bad validity check.
  • JLT-170800 - ConcurrentModificationException during Incident serialization
  • JLT-176215 - Fix paths not marked correctly as 'returned by exception' when using subpath-correlation.
  • JLT-172449 - Business Transaction stopped reporting data without reason
  • JLT-173323 - Missing business transaction result measures
  • JLT-175332 - Log spam when Frontend Server cannot connect to Performance Warehouse
  • ONE-5207 - fix IllegalArgumentException resp. NullPointerException in DtangAdapter
  • JLT-154333 - Collector grouping causes load balancing task to behave weired, if only one Agent connected (Agent was forced to bounce around the Collectors).
  • JLT-173248 - Collector does not start because of empty .ini file - make writing the .ini file more robust
  • JLT-176948 - A newly created infrastructure exclusion rule can't be saved

WebserverAgent

  • JLT-171042 - Use default agent configuration whenever a sub agent detects a shared memory version mismatch to turn that sub agent off.
  • JLT-171041 - Update shared memory file version manually to avoid unnecessary incompatibility issues between master and sub agents.
  • JLT-176227 - Improving debugTrafficNative logging for gzip-related problems.
  • JLT-165484 - IIS Agent causes a content length mismatch when the two newlines after the response header section are split into two fragments
  • JLT-171206 - Adding support for metrics for recent builds of IIS 10.

MainframeAgent

  • JLT-175226 - Test mode only: During playback of a zosEventsNative dump file, timing problems and crashes.
  • JLT-175438 - zRemoteAgent to properly unregister subagents of an unresponsive zLocalAgent

WebUI

  • JLT-169970 - WebUI: Show actual timeframe if server response deviates from selected request timeframe for world map and user analytics.

ServerCorrelation

  • JLT-175619 - Introduction of custom tagging up/down-link information collection for easier debugging of custom tagging problems.
  • JLT-175645 - CorrelationNG: change the default transaction buffer.
  • JLT-176249 - ForceAsync state on PurePaths is not correctly stored when CorrelationNG is enabled
  • JLT-174008 - CorrelationNG: fix resolving of OneAgent's WebRequest session attributes.
  • JLT-176137 - Applications are not correctly set when using SubPathCorrelation and OneAgent
  • JLT-176158 - Fix ConcurrentModificationException while propagating properties from serverside transactions to enduser transactions.
  • JLT-175630 - Sub-paths with non-unique custom tags are linked to path who are unlikely to be their parents considering difference in sub-path start time and down-link entering time because this time difference was not considered.

Collector

  • JLT-175909 - .NET Agent: Delayed monitored application startup caused by log spam inside Collector.
  • JLT-171391 - Incorrect data for some files in tablespaces report from Live View for Oracle DB Agent.

OneAgent

  • ONE-5045 - Nginx OneAgent causes worker processes to hang when injecting into large gzipped HTML pages.
  • ONE-5104 - Nginx agent causes worker processes to hang after a reload if proxy_cache config directive is used.

Mobile

  • ONE-3074 - Android agent: unify settings configuration for Dynatrace gradle plugin

6.5.7.1500 Resolved Issues

27 (+ 4) critical issues, 365 (+ 68) total resolved issues

 Component change overview
ComponentTotalNew
UEM5510
PWH92
Server11919
JavaAgent141
Client4811
WebUI224
ServerRTA60
Collector247
MainframeAgent123
NGINXAgent51
Mobile151
WebserverAgent113
ServerCorrelation164
OneAgent31
PHPAgent20
MessageBrokerAgent10
Communication10
DotNETAgent10
InstallerAndBuild11

Most critical issues since the last public updates

NGINXAgent

  • JLT-171274 - Chunked deflated datastreams caused nginx to hang.
    • Impact: Nginx got unresponsive and worker processes had 100% CPU utilization.
    • Cause: End-of-stream detection of chunked deflated datastreams did not work in all situations.
    • Solution: Corrected end-of-stream detection in chunked deflated datastreams.

Collector

  • JLT-171098 - Database Agent: too many log entries caused by connection problems.
    • Impact: Unreadable logs for collector
    • Cause: All errors on connection where logged
    • Solution: When connection error occurs, system suspends logging it for next 5 [min]

MainframeAgent

  • JLT-174301 - zRemoteAgent crash while handling subagent license verification.
    • Impact: The zRemoteAgent will crash, and need to be restarted.
    • Cause: The message handlers were not fully initialized when the license verification was received.
    • Solution: Verify that the handlers are initialized, and if not, wait for the next 5 minute DTAX cycle.
  • JLT-174941 - Excessive sequence errors and timeouts, due to high zRemoteAgent cpu usage, which also fills the SMO buffer
    • Impact: The prevented the zRemoteAgent from being able to read the socket, so the zLocalAgent couldn't empty the SMO which caused sequence errors.
    • Cause: A bad log message was using too much cpu.
    • Solution: Fix the log message to only execute the toString() if FINEST is set.

All resolved issues

Server

  • JLT-172315 - Potential error message when trying to read deleted session due to missing null check.
  • JLT-173279 - Fix storage of linking sensor id when using CorrelationNG.
  • JLT-172738 - Improve log output in ProcessHealthCalculator
  • JLT-102937 - Server log spammed with log entries like "Discarded JMX/PMI or PerfMon event due to..." after dtServer restart while dtCollectors running.
  • JLT-175159 - Duplicated/nameless incidents created from Monitor Measures
  • JLT-175343 - Error in Error detection Dashlet due to an EmptyStackException, added empty check and logs.
  • JLT-174084 - AvailabilityCenter log spam on SUD connector reassignment.
  • JLT-171962 - Per system profile permissions ignored for "Show Database Monitoring", "Manage Database Monitoring"
  • JLT-171431 - Hosts of connected java oneagent don't show up in hosts overview
  • JLT-171897 - Message handling improvements for OneAgents; Reduce log spam and log agent ids as formatted usually; Make a lot of settings configurable for potential tuning
  • JLT-170522 - Incorrect webservice-slow categorization due to missing persistance of config value.
  • JLT-165160 - Added license exhaustion information to dtactivation
  • JLT-173447 - ClassCastException when sub-path correlation is used and processing paths are accessed
  • JLT-172633 - NullPointerException in IncidentEngineUtils
  • JLT-173272 - Empty incident description when Chinese or Japanese language pack is in use.
  • JLT-158241 - Backend Process StackOverFlow caused by calling ErrorDetectionMeasure.clone()
  • JLT-171613 - Frontend Process: Running Low on Memory: Improve realtime mapping parsing performance
  • JLT-171686 - Copying and pasting a system profile that was created from a system profile template creates another template, not an actual system profile
  • JLT-171878 - SQL Bind values not considered as confidential in Database dashlet

Client

  • JLT-173005 - Certificate warning was not shown properly when Chinese or Japanese language pack was installed
  • JLT-171771 - The focus of dashlets is not set correctly causing problems when using actions of the dashlet header context menu (e.g. wrong dashlets being copied/renamed, filters being applied to wrong dashlets)
  • JLT-168991 - Client: StackOverflowError in ErrorDetectionMeasure.getKey(SourceFile:176) when editing "failed transaction percentage" measure source
  • JLT-174358 - Fixed an issue for comparing Test Results
  • JLT-173428 - Fixed an issue with wrong souce filters after a custom made drilldown was performed.
  • JLT-165243 - MWRT dashlet doesn't clear when all paths are filtered out
  • JLT-174461 - "ERROR-FORMAT-STRING Apache: {0}" showed in the health check screen for Apache OneAgent.
  • JLT-173450 - Fixen an issue concerning the Client toolbar's refresh item.
  • JLT-171619 - If an update installation was triggered from within the Start Center, the update wizard would close on the server restart step.
  • JLT-161517 - When a notification is shown the client would always be focused, thus defocusing whatever had the focus priorily.
  • JLT-174454 - Fixed an error when a Sensor Configuration was selected in Linux

MainframeAgent

  • JLT-173194 - Fix Version....... build date/time stamp for the zLocalAgent
  • JLT-174301 - zRemoteAgent crash while handling subagent license verification.
  • JLT-174941 - Excessive sequence errors and timeouts, due to high zRemoteAgent cpu usage, which also fills the SMO buffer

Collector

  • JLT-173433 - RMI sensor causes VerifyError with Weblogic 12.2.1.2
  • JLT-172260 - Plugins cannot be installed if Collector updates are disabled due to a NullPointerException
  • JLT-171915 - Improve throughput of Collector's CyclicSender for OneAgents
  • JLT-171098 - Database Agent: too many log entries caused by connection problems.
  • JLT-170531 - NullPointerException on unexpected MySQL response.
  • JLT-174925 - ClusterTime synchronization between Collector and Server takes too long making times on OneAgents unnecessarily inaccurate
  • JLT-172842 - Lowered logging message level due to it being non-actionable.

Mobile

  • JLT-166014 - iOS Agent: support for RATreeView (can be enabled with DTXSpecialDelegateHandling flag)

WebUI

  • JLT-171757 - WebUI: enforce Client dashlet permissions for the PurePaths view ('Analyze PurePaths'), visits view ('Analyze Visits'), and infrastructure views ('Show infrastructure'). To enable the additional checks, set the debug flag 'com.dynatrace.diagnostics.webui.enforceClientPermissions' to 'true'.
  • JLT-166444 - Added alternative country name support to the world map.
  • JLT-166627 - Selecting and deselecting splitting values in the edit measure panel produces inconsistent results when a filter is active.
  • JLT-175790 - Opening measure editor may remove all configured splitting values from measure if no data is available.

OneAgent

  • JLT-173377 - ASP.NET Core agent causes correlation errors when node reduction optimization is enabled

NGINXAgent

  • JLT-171274 - Chunked deflated datastreams caused nginx to hang.

UEM

  • JLT-171299 - NullPointerException on Java agent when UEM config is sent to a non-migrated agent with a JavaScript agent version that wasn't migrated either.
  • JLT-168553 - RxVisitor cookie occurs on some instrumented websites.
  • JLT-175163 - If a page leave is aborted, some JavaScript agent values aren't reset, which might lead to 180 second timeouts.'
  • JLT-173867 - Enable DrillDown from visit to Client Errors if visit has no failed action but JavaScript errors
  • JLT-171687 - reduce time-tolerance for linking web requests to actions in order to avoid wrong linked web requests due to long running actions.
  • JLT-172882 - Make UEM correlation more tolerant when linking web requests to actions in case page context exactly matches (don't check referer in this case)
  • JLT-172672 - Perceived render time URL may contain full image-data and thus invalidates beacons.
  • JLT-173327 - Bandwidth calculation was always downloading all 6 image files irrespective of connection speed.
  • JLT-172055 - XMLHttpRequest actions time out if beforeunload event is aborted by a user.
  • JLT-174389 - Non-http protocol href values trigger fake beforeunload causing action timeouts

PWH

  • JLT-172746 - Added option to repair metadata table of performance warehouse schema.
  • JLT-173053 - Very long incident properties cause a PWH exception (Data integrity violation)

ServerCorrelation

  • JLT-174678 - CorrelationNG: fix handing over empty transactions.
  • JLT-172331 - Fix inconsistent error detection data when using CorrelationNG.
  • JLT-173996 - Debug log spam for sub-agent events because corresponding filter was not applied.
  • JLT-172783 - PurePath was not marked as timed-out (pre-condition: no corrupted sub-paths), if any sub-path was timed-out because timeout was not propagated.

WebserverAgent

  • JLT-171696 - Nginx agent crash when handling large POST uploads.
  • JLT-172262 - Improving debugTrafficNative logging of binary data.
  • JLT-169143 - URI Filter does not work with empty query or URI and match set to "contains"

JavaAgent

  • JLT-171647 - PreparedStatement.execute() does not have SQL attachment anymore (if thread sensor is active below a jdbc method)

InstallerAndBuild

  • JLT-172837 - License text file was outdated

6.5.6.1013 Resolved Issues

Most important issues since the last public updates

Client

  • JLT-172306 - Client connecting to a Server with different version may cause a serialization error and thus shows no items in the Action Center
    • Impact: The Action Center does not show items but a general error message
    • Cause: Version check was incorrect
    • Solution: Version check was adjusted

UEM

  • JLT-171605 - AngularJS module breaks the page when expecting the version object
    • Impact: A "Cannot read property 'full' of undefined" error gets thrown every time XHR calls are made with angular, which breaks page functionality.
    • Cause: Angular module tries accessing the 'version' property after original global angular object was modified by customer code
    • Solution: Store the version string reference upon initialization of the module for later use

ServerCorrelation

  • JLT-171788 - Server crash due to stack overflow during completeness check of very deep PurePaths.
    • Impact: Server crashes.
    • Cause: Stack overflow during completeness check of very deep PurePaths.
    • Solution: Very deeply nested PurePaths are no longer checked for completeness in one but several steps.

Server

  • JLT-168999 - Possible temporary log spam from PureLytics when PWH gets disconnected
    • Impact: Some additional log entries when the PWH gets disconnected.
    • Cause: The PWH gets disconnected and the next time PureLytics-records get flushed to the PWH, the warning is logged for each PureLytics configuration.
    • Solution: Better suppress the warnings.

All resolved issues

Client

  • JLT-128883 - Controlled Fixpack Rollout: Update Wizard shows incorrect number of selected (to be updated) agents
  • JLT-145634 - Prevent unintended creation of BT and measure duplicates
  • JLT-165817 - A text in the UEM configuration dialog would not scale correctly on high dpi screens.
  • JLT-165877 - Fixed a scrolling issue for Network and Disk charts in the Host Details View.
  • JLT-171054 - Fixed an issue where a fresh session could crash the TransactionFlow.
  • JLT-171090 - Opening dashlets from different servers via the cockpit now have the correct sources set.
  • JLT-172306 - Client connecting to a Server with different version may cause a serialization error and thus shows no items in the Action Center

Collector

  • JLT-149244 - Plugin exceptions are logged in Collector logfile
  • JLT-170763 - Fixed a very rare connection interruption between collector and server.

JavaAgent

  • JLT-153378 - Resolved deadlock that could occur with dynamic classes and load balancing.
  • JLT-169418 - Added trackexcludedclasses agentpath option to reduce gc impact on IBM VMs with a high count of dynamically created classes.
  • JLT-170782 - Log spam because of getMessageBodyStyle not found in class com.ibm.mq.jms.MQQueue

UEM

  • JLT-155524 - reset BT calculation values before starting analysis for a new visit, otherwise BT results get corrupted.
  • JLT-158651 - Splittings for Visit BTs were mixed up because of interference with splittings of server side PurePaths
  • JLT-159316 - JSAgent XHR plugin: Upload fails with "TypeError" error when polyfill is present on Array.
  • JLT-160417 - Optimize RealtimeBtmEndUserPageActionAnalyzer.analyzeExecPathEnd -> remove which might have influence on RTA performance
  • JLT-164769 - Inline JS Agent causes XML-Exceptions and is not CSP-Compliant.
  • JLT-166419 - handle invalid values in W3C navigation timing more smoothly instead of dropping whole attachment.
  • JLT-168444 - If a link redirects to a different subdomain, Dynatrace doesn't capture the click on the link even if both pages are instrumented.
  • JLT-169198 - Only book measures from server-side PurePath on visit, if PurePath is not linked to an action. Booking is therefore delayed and done by VisitStoreAgingTimer as soon as we definitely know, that a server-side Path is not linked.
  • JLT-170447 - Evaluate event time before adding to UEM queue and add queue limit in order to prevent endlessly growing UEM queue.
  • JLT-170969 - all reported values are handled as strings -> reportDouble must end as double and reportInt as int.
  • JLT-171083 - First Party and CDN mappings don't work for same top-level domain if requested via www.domain.com.
  • JLT-171277 - Added the new name of Czechia as an alternative name for the Czech Republic.
  • JLT-171605 - AngularJS module breaks the page when expecting the version object

WebUI

  • JLT-162790 - The sorting of the table in the BT list detail view does not work correctly.

PWH

  • JLT-163400 - connection status get stuck on "Synchronizing system profiles..."
  • JLT-170248 - Malformed SQL in DB2 performance warehouse, fixed with alternative statement.

ServerCorrelation

  • JLT-164965 - Enable processing of autosenssor data from OneAgents.
  • JLT-165942 - PurePaths are corrupted with stalled global agent time as reason, because global agent time jumped to past (e.g. due to agent unregister), even though required time for corruption did not pass on server.
  • JLT-169828 - Fix 'previous element of ring buffer must never be null' warning.
  • JLT-171788 - Server crash due to stack overflow during completeness check of very deep PurePaths.

Server

  • JLT-168941 - In the host overview there are no network values visible
  • JLT-168999 - Possible temporary log spam from PureLytics when PWH gets disconnected
  • JLT-170253 - Fix potentially incorrect counts in error-detection dashlet.
  • JLT-170648 - EntryPoint analyzer incorrectly distinguishes the same method from different agents or sessions.
  • JLT-170672 - Method return value {0} is not resolved for external API
  • JLT-170700 - Improve session reading performance when lots of threads are involved on purepaths.
  • JLT-170753 - Web server health dashlet not showing any data for Nginx OneAgents
  • JLT-170767 - External HTTP call is not shown in WebRequest dashlet
  • JLT-170843 - Fix potentially non-matching counts in ErrorDetection and ErrorDetection Details.
  • JLT-170960 - Improve session reading performance for visits.
  • JLT-170967 - Allow to explicitly set read direction of visit- and purepath analyzer via flag
  • JLT-171088 - Problem opening server settings dialog when server-collector connection or collector is stalled.
  • JLT-171448 - Fix a potential race-condition between continuous integration component and session storage that can lead to lost CI data
  • JLT-171645 - Fix log spam when OneAgents are being removed due to timeout.
  • JLT-171670 - Update GeoIP Databases and User Agents to prevent outdated mappings or unknown User Agents
  • JLT-171898 - Fix an issue where the server would spam OneAgents with identification requests when they would connect via a collector

WebserverAgent

  • JLT-170264 - Protocol error in the webserver agent causes Collector restarts due to a full socket queue.

ServerRTA

  • JLT-170836 - Fixed the number of threads for the categorization which was possibly too low for agents that do not provide thread information.
  • JLT-171177 - NullPointerExceptions if request with host-header constisting only of ".." is processed.
  • JLT-171851 - ArrayIndexOutOfBoundsException by clicking on "Create Measures" on database PurePath

Mobile

  • JLT-171203 - Android agent: increased Java heap size for auto-instrumentation (for Windows)
  • JLT-171450 - Android Agent: patch aapt to provide missing application-label output to avoid client crash in instrumentation wizard

6.5.5.1018 Resolved Issues

Most important issues since the last public updates

ServerRTA

  • JLT-169819 - Agent group selection on measure config changes on it's own without user intervention
    • Impact: Measures get only booked for the selected agent group (Missing data in charts)
    • Cause: DefaultMeasureKeyCache sets a single agent group on the original config measure
    • Solution: Cloning the config measure in the RealtimeAnalysis config

Server

  • JLT-169581 - WebUI shows error message "A fatal internal server error occurred. Please check the log files." in Infrastructure- and Hosts-view.
    • Impact: WebUI shows error message instead of a list with hosts
    • Cause: NullPointerException in HostIdentifier (Server) when accessing Host information
    • Solution: Make sure the requested Host information is available or use default value if not
  • JLT-170420 - MQ Mapping with custom tagged PurePaths: Unlinked PurePaths
    • Impact: Some MQ mappings (custom tags based on MQ data), which rely on a proper setup of the server side MQ mapping structure, failed causing unlinked MQ custom tagged pure paths.
    • Cause: With startup optimizations reading mqmappings.xml (Client and Server) a regression was introduced in building up the internal server side MQ mapping structure only partially.
    • Solution: The full server side MQ mapping structure preparation is now again performed with server startup, while it is still omitted in the client side (where MQ mappings are not needed anyway).

WebUI

  • JLT-169325 - Simple node details breaks scrolling in the entire WebUI (touch-devices only) after opening node details in transaction flow.
    • Impact: Scroll events were cloaked by the drag behaviour.
    • Cause: There were 2 overlaying drag behaviours which caused a interruption of the touch event chain. So some of the handlers were not removed and caused a cloaking of the scroll events.
    • Solution: Removed the second drag behaviour and moved background click detection to zoom behaviour.

UEM

  • JLT-168828 - Documents which are exported via PureLytics Stream will be dropped if the contain '.' in field names
    • Impact: Missing User Actions and Visits.
    • Cause: BT names will be added as field in the exported document. BT names can contain '.', which are prohibited in fields by Elasticsearch
    • Solution: Replace '.' with '_' in field names.
  • JLT-170776 - OneAgent configuration: fixed auto-prepended jsagent features per InjectionStrategy
    • Impact: no user-actions when using single-tag injection with one-agent, potential JS errors in the page
    • Cause: Asynchronously injected JS agent received core module twice, whereas single-tagged injected JS agent did not receive a core module at all.
    • Solution: Bumped OA configuration version to 1.34.0 (containing the fix where auto-prepended features were switched between strategies)

Collector

  • JLT-170167 - Wrong DB Agent connection pool usage may cause broken connections to be kept in the pool.
    • Impact: In case of network problems, the pool may accumulate broken connection preventing DB Agent from working.
    • Cause: DB Agent connection pool is not using validation query to check connection state.
    • Solution: Added validation query to the pool used by DB Agents.

Client

  • JLT-168426 - Server certificate evaluation in the client received more data than necessary.
    • Impact: Potential leakage of the private key due man-in-the-middle attack.
    • Cause: The private key of the server was unnecessarily sent to the client for certificate evaluation.
    • Solution: Only provide necessary data of the server to the client for certificate evaluation.

ServerCorrelation

  • JLT-169805 - Pure-path information is dropped due to corrupt paths as result of agent disconnects.
    • Impact: Pure-path information is dropped.
    • Cause: Tried to add information about involved agents/threads to completed pure-path.
    • Solution: Do not throw exception but log only.

All resolved issues

ServerRTA

  • JLT-150888 - Execution/CPU times per API differ between Layer Breakdown, API Breakdown and PurePath view
  • JLT-169819 - Agent group selection on measure config changes on it's own without user intervention

Server

  • JLT-159566 - Resource dumps are deleted now even if there is still enough storage space available. Not enabled per default!
  • JLT-159751 - Fix problem with saving a systemprofile when a manual-recording of this systemprofile is running. Disable the possiblity to reanalyze an in-progress session.
  • JLT-164912 - Incidents are duplicated under certain circumstances; incident names, descriptions and messages are missing or wrong under certain circumstances.
  • JLT-165090 - Improve session-reading performance for visits in case lots of visit-sessions must be read.
  • JLT-165110 - Unable to apply host filters to monitor measures due to different host name and host address
  • JLT-167226 - Fix race condition during server shutdown.
  • JLT-168933 - NullPointerException in PdkBeanFactory30
  • JLT-168964 - Fix missing business transaction drill-downs from purepath dashlet.
  • JLT-169112 - Fix race condition when processing CPU sampling events while the CPU sampling task is closed.
  • JLT-169136 - Security/Keystore refactoring to reduce code complexity
  • JLT-169397 - Fix NPE happening due to race condition during server shutdown.
  • JLT-169400 - Fix a potential Nullpointer-Exception during Session-Reanalysis.
  • JLT-169425 - Uncaught NullPointerException in HostIncidentUtils
  • JLT-169581 - WebUI shows error message "A fatal internal server error occurred. Please check the log files." in Infrastructure- and Hosts-view.
  • JLT-169613 - Cannot find a matching SUD for the agent in AvailabilityCenter on agent state update
  • JLT-169829 - Implement MQMapping debug flag as com.dynatrace.diagnostics.debugMQMapping
  • JLT-169918 - Out-of-range measurements (e.g. -1) for self-monitoring-measures cause PWH incident to fire.
  • JLT-169919 - Fixed slowdown of session storage when requested session was not available any more.
  • JLT-169932 -  Backend Server: CI data processing can experience ClassCastException in OnVisitEnd due to missing synchronization 
  • JLT-169967 - Improve session reading performance for Visits when a business transaction filter is set.
  • JLT-170243 - Improvement in session reading performance.
  • JLT-170420 - MQ Mapping with custom tagged PurePaths: Unlinked PurePaths
  • JLT-170438 - Prevent log spam when CAS-UEM integration is disabled by debug flag
  • JLT-170556 - TimeKeeper warning "Skipping [..], incident resolution might be lower than expected."
  • JLT-170568 - Fix a potential ChannelClosedException during session reading.
  • JLT-170691 - IllegalArgumentException in Agent overview for nginx OneAgent

WebUI

  • JLT-162450 - Sorting behaviour is broken in BT list detail view
  • JLT-168443 - WebUi: Transaction flow: If a group contained only nodes of the type application, no links to visits where displayed in the group's details panel.
  • JLT-169325 - Simple node details breaks scrolling in the entire WebUI (touch-devices only) after opening node details in transaction flow.
  • JLT-169458 - Essential controls are not visible in tile config view when using iOS

JavaAgent

  • JLT-163462 - Agents sometimes not reconnecting with Collector after LoadBalancing/FailOver
  • JLT-164616 - WebMethods HttpURLConnection via proxy suppresses servlet PurePaths
  • JLT-168965 - Timer logs may be written to console on loglevel none.

WebserverAgent

  • JLT-164607 - Introducing debug flag "debugSuppressWebRequestHeaderModificationNative" as a workaround for cases where the request headers set for agent-to-agent communication aren't tolerated by the backend.

UEM

  • JLT-165894 - NumberFormatException for beacon signal due to large latC value: use NumberUtil to convert string to int instead of Integer.parseInt
  • JLT-166465 - Browser's resource timing values are deleted if UEM is active.
  • JLT-168828 - Documents which are exported via PureLytics Stream will be dropped if the contain '.' in field names
  • JLT-170028 - Fix evaluation of mobile web request measure (only worked with contains)
  • JLT-170776 - OneAgent configuration: fixed auto-prepended jsagent features per InjectionStrategy
  • JLT-171295 - Resource timings might be sent multiple times, which can lead to duplicate resources in a User Action PurePath.

Collector

  • JLT-165895 - Additional log outputs on establishing/validating DB Agent connection
  • JLT-167147 - Problems, when class cache clean-up is running during shutdown.
  • JLT-168661 - When collector runs out of memory during class cache clean-up, subsequent class cache clean-up runs fail, even if there is enough memory.
  • JLT-168703 - Java 8 instrumentation can lead to NoSuchMethodExceptions with serialized lambda expressions.
  • JLT-168918 - Add support for jobname in IMS Subagent naming
  • JLT-170167 - Wrong DB Agent connection pool usage may cause broken connections to be kept in the pool.
  • JLT-170660 - Log spam (FINE) in collector log

Client

  • JLT-168426 - Server certificate evaluation in the client received more data than necessary.
  • JLT-168637 - The show on startup checkbox in the start center is not shown for non production licenses.
  • JLT-168853 - Nightmode issue in the WorldMap
  • JLT-169197 - Ensure that expand possibility does not get lost on searches in cockpit.
  • JLT-169264 - The CICS Sensor Configuration Dialog does not show all options on 1024x768 screens.
  • JLT-169966 - BT context information missing on chart drilldown
  • JLT-170091 - NPE when trying to create Method measures in Method Hotspots dashlet.
  • JLT-170124 - License overview now displays "local agent connections only" for personal licenses only.

MainframeAgent

  • JLT-169015 - 6.2 and 6.3 bootstrap dtzagent on z/OS won't bootstrap from a newer zRemoteAgent >= 6.5.3

NGINXAgent

  • JLT-169330 - Nginx purepaths timeout when served via the pagespeed module having a cache hit.
  • JLT-169975 - Nginx agent responds to mobile time sync requests with an invalid content length header.

Mobile

  • JLT-169406 - CocoaPod documentation update.
  • JLT-169925 - iOS Agent: Potentially memory corruption at high load scenarios.
  • JLT-170108 - Android Agent: VerifyError on Android 5.0+ devices when auto-instrumentor property DTXBKSPassword is used
  • JLT-170551 - Android Agent: Updated Android build tools for supporting Android 7.0 feature (requires Java 1.8)
  • JLT-170566 - Android agent: improved HttpUrlConnection auto-instrumentation for Android 7.0 devices

ServerCorrelation

  • JLT-169805 - Pure-path information is dropped due to corrupt paths as result of agent disconnects.
  • JLT-170426 - Fix handling of start-path events with custom tagged uplinks during memory shortages.

OneAgent

  • JLT-170414 - Added runtimeconfiguration for logging sensor (one agent)

6.5.4.1014 Resolved Issues

Most important issues since the last public updates

UEM

  • JLT-167670 - AngularJs module does not invoke correct multiple success callbacks
    • Impact: Main success callback does not get invoked, resulting in unexpected page behavior
    • Cause: Mutable variable is accessible from closure when looping through callback arguments to invoke
    • Solution: Define callback wrapper within self invoking function

Server

  • JLT-167281 - Due to inconsistent data retrieved from OS a single WOSI can consume multiple licenses.
    • Impact: Agents on one Windows instance will consume multiple licenses when they see different Windows boot times.
    • Cause: Method to retrieve Windows Boot Time doesn't return reliable values.
    • Solution: Windows boot time will not be considered anymore for license check.

All resolved issues

WebUI

  • JLT-135007 - Allow setting a description of tiles on web dashboards.
  • JLT-160545 - "show only last value" setting is ignored for pie, meter and area chart ordering.
  • JLT-161525 - NOC mode support for chart tiles.
  • JLT-161526 - NOC mode support for all non chart tiles.
  • JLT-161527 - NOC mode support for dashboards.
  • JLT-162422 - Documentation link for configuring synthetic tiles leads to wrong page.

UEM

  • JLT-142377 - Collector logs excessively if JS Agent version is set to 'latest', but connected agent is not yet updated.
  • JLT-165744 - only dtAdkTag cookies ending with _0 are ignored now instead of ignoring all ending with 0
  • JLT-166514 - jQuery (1.7 and below) aborted XHRs in ajaxPrefilter results in action timeout
  • JLT-166515 - World Map dashlet: Fixed filtering by application when displaying active visits.
  • JLT-166634 - "Access-Control-Allow-Origin" not set on JS agent requests
  • JLT-167670 - AngularJs module does not invoke correct multiple success callbacks

Server

  • JLT-159394 - Transaction flow sometimes doesn't calculate times correctly for callers of external services.
  • JLT-164397 - Fixed error handling when system profile creation fails.
  • JLT-165213 - Storing EndUserErrorRecords in the PWH may cause out-of-memory situations on the server
  • JLT-165898 - Failed FQDN lookups spamming the log
  • JLT-165934 - Webstart Client startup requires multiple authentications (Java Web Start authentication dialogs)
  • JLT-166741 - Filters get lost if timeframe is changed in HTML reports
  • JLT-167229 - Improve and throttle log output in case of exception in HostMetricCenter and HostTimeSeriesTimeoutNotifier
  • JLT-167281 - Due to inconsistent data retrieved from OS a single WOSI can consume multiple licenses.
  • JLT-168439 - Server reports of Errors dashlet do not contain the details section although the according debug flag is set.
  • JLT-168458 - Schedules: On the day when daylight saving time is changed, a task scheduled between 2 AM and 3 AM might not run
  • JLT-168494 - Online check was not performed correctly when importing an online license for the first time.
  • JLT-168736 - Allow embedded Performance Warehouse and Collector for FreeTrial online license
  • JLT-168792 - Application/agent group filtering for web request measures with same configuration not working properly
  • JLT-169316 - Sending scheduled report emails uses wrong mailserver configuration

Client

  • JLT-159685 - Database dashlets (LiveView and Details) were unable to restore stored columns order

Collector

  • JLT-161123 - Reduce the disconnected agent shutdown timeout from 1 minute to 30 seconds. This should help avoid the GAT to stop if agents are killed.
  • JLT-164353 - Avoid a possible NullPointerException that may happen during Collector startup by changing initialization order.
  • JLT-166464 - JDBC connections opened during testing of DB Agent configuration are not closed properly.
  • JLT-168673 - Rare Null Pointer Exception during network interface lookup

PWH

  • JLT-161859 - Performance Warehouse System Profile Import Task: Time Unit for percentiles is interpreted as days instead of hours
  • JLT-164335 - Performance Warehouse Exception Incidents are never closed in certain circumstances
  • JLT-168706 - Frontend Server log contains unique constraint violation exceptions

PHPAgent

  • JLT-164937 - Improve PurePath displaying for PHP 7 OneAgent

ServerCorrelation

  • JLT-165235 - Purepaths are visible as subpaths and transactions due to a race condition in a non-unique custom tagging scenario.

Mobile

  • JLT-166563 - iOS Agent: reported invalid battery level
  • JLT-167331 - iOS Agent: log agent configuration if loglevel >= FINER

MainframeAgent

  • JLT-167236 - zRemoteAgent should not disconnect when receiving messages from unregistered subagents
  • JLT-167334 - Fix PHP one agent "System Profile version xxx could not be synchronized"

NGINXAgent

  • JLT-168750 - Nginx agent fails to clean up memory and file descriptors during an Nginx reload.

 

 Click to expand 6.5.4 WebUI NOC mode feature

This update to the AppMon & UEM web dashboards is all about making your day more effective. You know which workflows are most effective in case of a problem. You know which team members you need when the heat is on. And you explain the data you share and report, so your teams can yield the most value from your expertise. And use the new dark mode for web dashboards wherever you need.

        Get AppMon 6.5 for SaaS

Web dashboards for IT-operations

Whether at your desktop, in a meeting or on the go - the web dashboards are your daily companion. And now, with the dark mode, you can use them in your IT-operations center too.

Unveil your collective intelligence

This update introduces markdown annotations for web dashboard tiles. This allows you to explain the data you show - and by leveraging the full markdown capabilities you can even connect dashboards with workflows and further resources you need to resolve problems.

  • Custom workflows: Include links with predefined filters to drill down to multiple workflows.
  • Share your knowledge: Links, tables, and much more. The markdown syntax sets no limits for adding additional information to your dashboards

 

Visual Studio 2017 integration and more...

Dynatrace is a Microsoft PremierPartner and we are proud to announce the availability of the AppMon Visual Studio integration on the Visual Studio Marketplace right on time for this week's release of Visual Studio 2017. You can download it either directly from the Marketplace or install it directly from the Extensions and Updates dialog in Visual Studio. This extension allows you to

  • automatically look up your source code from the Dynatrace AppMon client in Visual Studio,
  • launch your .NET applications with an injected Dynatrace agent and
  • run your unit tests with the Dynatrace agent.

Looking for PHP7 support? Check out our new agent for PHP7 including new agent features . Click here to get started!


6.5.3.1013 Resolved Issues

Most important issues since the last public updates

Client

  • JLT-164408 - Added additional host names configurator for Database Agent configuration window.
    • Impact: Modification of Database Agent configuration window.
    • Cause: Implemented due to several customers reporing a problem with automatic mapping Database Agents to system profiles.
    • Solution: Added new popup dialog with additional host names configuration.
  • JLT-164454 - Secure email connections can not be properly configured
    • Impact: User may run into TLS / STARTTLS connection problems
    • Cause: User may run into TLS / STARTTLS connection problems when secure or plaintext SMTP was selected
    • Solution: Provide more connection types for Email configuration and fix a bug disallowing to configure port

All resolved issues

Server

  • JLT-165687 - Renewal information was lost when deactiving a perpetual usage based volume.
  • JLT-165813 - Avoid PurePaths to get corrupted when the global agent time jumps to the past for a very short time (which currently can happen when an agent gets balanced)
  • JLT-157433 - Add system property to prevent server web interface being opened in frames.
  • JLT-160157 - Add crossframe scripting prevention mechanisms (HTML Reports).
  • JLT-161064 - Add crossframe scripting prevention mechanisms (tabbed HTML Reports).
  • JLT-164848 - Drilldown from aggregated external calls in Transaction Flow doesn't work.
  • JLT-160315 - NPE occurred during serialization of infrastructure data due to missing session
  • JLT-160341 - Logspam when processing test data from UEM Agent
  • JLT-161089 - RealtimeExceptionAnalyzer marks oneagent "captured exception" as false "intertier exception"
  • JLT-161351 - Integrity check fails on system profile clone after creating agent group from template
  • JLT-162037 - NullPointerException in SysInfoCenter when no connection could be acquired from already established communication session with Memory Analysis Server
  • JLT-162814 - Required CPU speed should have some tolerance
  • JLT-162827 - Log the required and the detected CPU speed in the server log(s)
  • JLT-165862 - Deleting and creating a monitor measure depending on a missing plugin can lead to an error during system profile saving.
  • JLT-165872 - Fix an exception when opening class-browser for a OneAgent class
  • JLT-165627 - Robustness improvement in logging backend

Client

  • JLT-163692 - Warning about default shipped server certificates was updated.
  • JLT-161878 - Spelling mistake in chart label on Database Details dashlet for MySQL.
  • JLT-163788 - Licensing wizard shows too few (-3) .net WOSI licenses.
  • JLT-131702 - Update deployment - "Restart Agent tiers" is (seemingly) empty, text only appears after resizing the window
  • JLT-158124 - On Mac and Linux the cockpit would scroll to the currently selected entry after expanding/collapsing a tree-node.
  • JLT-159556 - There was a weird white bar shown in night mode in the incident chart dashlet, unless the current as well as the historic state of an incident rule were healthy.
  • JLT-162603 - Chart rendering would fail with an IllegalArgumentException for charts whose timeframes were shorter than the interval of the highest available resolution at that time for bar-charts.
  • JLT-162829 - Client connection may get stuck during server shutdown
  • JLT-163210 - Empty Host dashlet when no connection to the server was available
  • JLT-163634 - The link to drill down to the analyze memory usage dashboard in the memory diagnosis section of the start center was missing.
  • JLT-163911 - Dynamic Measure Matrix passes incorrect application filter when using "Show in Dashboard"
  • JLT-164229 - Under some unlikely circumstances the visit-search would fail due to a java.util.ConcurrentModificationException.
  • JLT-165412 - The adavanced agent mapping dialog was far too large
  • JLT-158499 - The start center is always opened on the primary monitor of multi-monitor setups and not on the same display as the client.
  • JLT-164408 - Added additional host names configurator for Database Agent configuration window.
  • JLT-163431 - Email notification of incident assignment results in exception when no email address is configured for the assignee.

UEM

  • JLT-164893 - Fix IllegalPathModificationException in UEM correlation: deactivate handling for creating a root action based on a user action info in a root error.
  • JLT-154089 - Memory leak in JS Agent core with IE Compatibility Mode.
  • JLT-154926 - Perceived Render Time module doesn't capture images if they are loaded too quickly.
  • JLT-163882 - allow instrumentation of jQuery 3.1

WebserverAgent

  • JLT-149143 - Trailing semicolon in a cookie gets duplicated by the webserver agent.
  • JLT-163222 - Webserver agent causes oscillating sub agent states in case of a shared memory corruption.

WebUI

  • JLT-161076 - Missing icon and display name localization for observed tiers in the transaction flow.

JavaAgent

  • JLT-163608 - Added support for Jetty Http Client 9.0-9.3
  • JLT-166213 - The usebootstraploader agent option could cause misleading exception stacks.

Mobile

  • JLT-165917 - Android Auto-instrumentor now correctly aborts for multi-dex applications, if the resulting instrumented .apk file would crash (on Android 4.4 or lower) because of incorrectly moved classes.
  • JLT-161879 - Android Agent: custom okhttp3 interceptor blocks tagging of retrofit2 web requests Android Agent: remove unused/duplicate values from lifecycle events

Communication

  • JLT-159176 - HTTP TRACE allowed on port 8040/8041/8042/8043

PWH

  • JLT-166184 - No charting/transaction flow data visible in client after failed performance warehouse migration

Collector

  • JLT-161086 - False positive warnings "No native resources in bundle" for minified agentres (by design no native)
  • JLT-160327 - As AppMon customer I want to freeze the version of my Collector using a debug flag

MainframeAgent

  • JLT-165776 - zRA causes high CPU consumption if a 6.5 zRA is connected to a 6.2 zLA
  • JLT-165906 - Throttle log message when data events arrive without subagent INIT

6.5.2.1012 Resolved Issues

Most important issues since the last public updates

Server

  • JLT-160542 - Wrong href field value returned in response of register test run REST API endpoint.
    • Impact: Wrong href generated preventing automated tools from fetching test run data.
    • Cause: Wrong regex used when building the href.
    • Solution: Fixed regex.
  • JLT-160371 - DB Agent config update only partially visible on Server.
    • Impact: When DB Agent config is updated not all changes make it to AvailabilityCenter caches and in some cases it may cause problems with matching DB Agents to system profiles. Server restart is a workaround.
    • Cause: Not overwriting older cache entries.
    • Solution: Make sure old cache entries are overwritten.
  • JLT-159587 - TestOverview dashlet may present invalid number of browser test executions for recorded sessions.
    • Impact: Drill down from TestOverview dashlet to TestResults dashlet can may present different number of test executions than reported in overview dashlet.
    • Cause: Polling browser tests' data during the session recording may cause multiple aggregations of test executions.
    • Solution: Updated counting procedure to calculate only the latest executions of browser tests.

UEM

  • JLT-163612 - ActiveX sensor returns the wrong context in readyStateChange
    • Impact: references to 'this' in readystatechange handlers will not contain expected values, and thus would cause page breaking behavior
    • Cause: ActiveX sensor returns the wrong context in readyStateChange
    • Solution: readyStateChange function should be returning 'this' instead of the 'request' argument object

JavaAgent

  • JLT-165222 - Application detection ignores request query.
    • Impact: Application detection not working if rule includes query.
    • Cause: Caused by JLT-162228: Request query doesn't get passed to application detection method.
    • Solution: Append query to URL before passing it to application detection method.

All resolved issues

WebserverAgent

  • JLT-158261 - Webserver agents cannot access POSIX timer functions on some systems forcing the agent to use a fallback timer.
  • JLT-158274 - Webserver agents unnecessarily avoid using the POSIX timer and reinitialize the selected timer also on unrelated configuration updates.
  • JLT-160365 - Nginx agent occasionally truncates responses that were cached and then expired.

Server

  • JLT-159116 - Confusing message: MySQL DB Agent: Insufficent Privilegies when sys schema not available.
  • JLT-160446 - Max wait time for Live view results isn't configurable via debug flag.
  • JLT-160542 - Wrong href field value returned in response of register test run REST API endpoint.
  • JLT-165405 - User gets NPE in client on loading PPs or transaction flow due to dbagent data and lack of permissions
  • JLT-157617 - Changing BT name to one starting with the old name causes NPE
  • JLT-160371 - DB Agent config update only partially visible on Server.
  • JLT-164881 - Incidents don't show up in heat field due to ArrayIndexOutOfBoundException in TransactionPattern
  • JLT-165083 - Concurrency and cluster wait times reversed on db Slow queries view
  • JLT-165215 - Fixed license log in server log.
  • JLT-152118 - Rich client shows decoded URL queries while RTA uses encoded strings
  • JLT-157434 - Prevent reflected file download by adding filename to Content-Disposition header.
  • JLT-158093 - (Infrastructure)Exclusion rule with ignore doesn't influence host health status (only host health history)
  • JLT-158483 - Dynamic Measure Matrix - Bar visualization doesn't change color with threshold violation for host measures
  • JLT-159475 - Fix Postprocessing of Memory Snapshot with a remote AnalysisServer leaves raw file on disk and does not update size correctly in SessionManager.
  • JLT-159587 - TestOverview dashlet may present invalid number of browser test executions for recorded sessions.
  • JLT-160561 - Allow to disable following unknown downlinks during analyzer runs to improve analyzer performance via DebugFlag. Also never try to find a referenced path that has been disposed before
  • JLT-161418 - DB measurements retrieval spins in a tight loop if exception thrown
  • JLT-161800 - Correlation of OneAgent events may have been wrong when time between the DynaTrace server and the agents differs significantly
  • JLT-164618 - Authentication for server side online licensing fails due to missing password decryption.
  • JLT-164342 - Fixing regression: Errors dashlet shows wrong exception class name since 6.5

WebUI

  • JLT-159426 - Opening the color picker in the measure configuration view resulted in automatically overriding the default color.
  • JLT-164723 - World map does not show the correct visit count for Korea
  • JLT-160402 - The columns of the table in the Business Transactions detail view are not sorted correctly.
  • JLT-160829 - "Focus on most actual Value" setting is ignored for Min/Max aggregations.

NGINXAgent

  • JLT-159508 - Nginx agent causes requests to hang when used together with Nginx's auth_request module.

Mobile

  • JLT-164450 - Android instrumentation fails with NullPointerException: handle debug info optimization by dexguard 7.0
  • JLT-164364 - Rare deadlocks on main thread with iOS Mobile Agent on iOS 10.

Client

  • JLT-117603 - Drill-down from failure rate measures within charts does not work
  • JLT-158313 - Changed some built-in dashboards to have autorefresh of 5 minutes and their drilldowns opened in new dashboards.
  • JLT-158654 - Re-enable automatic reporting of error-detection details.
  • JLT-158792 - Method Hotspots Dashlet can use a lot of memory due to no Result Limit being considered for Details.
  • JLT-163180 - Error dashlet - Detail panel: Order by User Action column not working

UEM

  • JLT-158259 - Fixed "Failed to parse mobile tag" log spam: fixed handling of mobile tag, if PurePath is not started by sensor reading the tag.
  • JLT-164699 - fixed NPE when resolving clientIp with null string
  • JLT-159111 - HTML injection wouldn't find a suitable injection location in certain cases involving <script> tags before <html>.
  • JLT-159138 - Webrequests are incorrectly linked to actions that are already complete if no page change occurred for at least 15 minutes.
  • JLT-162477 - JavaScript exception with perceived render time module if images are removed during onload phase.
  • JLT-163140 - Abort event is fired two times if registered onto an instrumented XMLHttpRequest object via the "onabort" property.
  • JLT-164765 - JavaScript agent might not be on current version if fixpack is installed.
  • JLT-163323 - JS Agent's basic XHR module doesn't fire readystatechange event on IE 10 and lower if listener is registered after call to "open".
  • JLT-163612 - ActiveX sensor returns the wrong context in readyStateChange
  • JLT-157693 - javascript:void(0) clicks in IE compat mode trigger beforeunload event causing actions to timeout
  • JLT-161403 - Named functions in 'javascript:' also trigger a fake beforeunload event causing actions to time out

JavaAgent

  • JLT-165222 - Application detection ignores request query.
  • JLT-161297 - Elastic search sensor fails with "java.security.AccessControlException: access denied"
  • JLT-162322 - Cassandra agent isn't detected as NoSQL TechType
  • JLT-162228 - Application detection ignores host headers on servlet sensor.

DotNETAgent

  • JLT-162092 - Enables ASP.NET Impersonation with UEM Tagging support.

OneAgent

  • JLT-153913 - Fix IndexOutOfBoundsException on processing AutoSensor data from OneAgents that might happen early after startup.

MainframeAgent

  • JLT-159647 - zRemoteAgent sends an unnecessary full reconnect message when a sensor configuration is updated.
  • JLT-162854 - zRemoteAgent doesn't log subagent statistics.
  • JLT-164768 - zRemoteAgent should not disconnect when receiving an unwanted UNINIT.

ServerRTA

  • JLT-160144 - Custom Tagged SubPaths get analyzed twice.

PWH

  • JLT-160236 - Missing chart data after adding splitting to a Business Transaction

ServerCorrelation

  • JLT-160359 - ConcurrentModificationException in rare situations during realtime analysis of EndUser transactions.
  • JLT-161609 - Very deep linking of root execution paths may lead to stack overflow during completeness check and consequently to server crash.
  • JLT-162101 - Web request response time is unreliable when subpath contains async servlet processing
  • JLT-163027 - Improve logging to find the root cause for Early discarded PurePaths - empty root path.

Collector

  • JLT-160403 - Fix collector disconnect when clicking on "Open Hierachy" in add/remove sensor dialog of PurePath node.
  • JLT-159941 - Monitors create unexpected host splittings for measures after server restart.

PHPAgent

  • JLT-159055 - Incorrect informations about Oracle database name in PHP.

6.5.1.1003 Resolved Issues

Most important issues since the last public updates

Server

  • JLT-163041 - Running the same NUnit test in multiple threads may cause concurrency errors.
    • Impact: Multiple concurrent corridor calculations for the same test may cause log spam and incorrect corridor results.
    • Cause: Multiple threads were concurrently accessing the same measures history, causing concurrency exceptions.
    • Solution: Provided thread-safe corridor calculation procedure.

MessageBrokerAgent

  • JLT-162427 - Redhat 5 fails to load agent on websphere MQ brokers
    • Impact: Redhat 5 on zLinux for s390/x fails to load dynatrace agent on websphere MQ brokers.
    • Cause: Websphere MQ broker agent binaries were not built for for Redhat 5 on zLinux for s390/x.
    • Solution: Re-enable websphere MQ broker support for Redhat 5 on zLinux for s390/x.

All resolved issues

Server

  • JLT-160305 - UEM Test Automation: No Server Side Measures after they are enabled in profile until server restart.
  • JLT-158966 - Null pointer check added in Rate Measure calculation for charting
  • JLT-162461 - Do not always reduce buffer size by 50% after a full gc
  • JLT-163041 - Running the same NUnit test in multiple threads may cause concurrency errors.
  • JLT-163355 - JVM-specific measures will not be subscribed for a newly created system profile
  • JLT-160805 - Backend Server: Deadlock ApiMeasureSubscriberTask/ApplicationSession

MainframeAgent

  • JLT-162091 - zLocalAgent crash during a disconnect cycle.

JavaAgent

  • JLT-164225 - Fixing a potential SecurityException on AIX

UEM

  • JLT-160108 - Initialization code of asynchronously injected JS Agent cannot be delivered if upgrading from an EAP version of 6.5 to GA without restarting the agents.
  • JLT-162466 - Fix timestamp and start/endView handling in new mobile protocol
  • JLT-163142 - Handle start/endView in new mobile protocol correctly
  • JLT-163472 - fixed transformation of startAsync -> initialize dtUemReturnValue with null. Needed for the case when startAsync is implemented without a return value but throws an UnsupportedOperationException
  • JLT-163710 - It is not possible to activate the async JS Agent setting without changing any other configuration field. If a new system profile is created, async is enabled in the client, yet not configured on the agents.

WebUI

  • JLT-160554 - Chart series don't have the same order as a custom splitting list.
  • JLT-162050 - Invalid point resolution in percentile tile causes broken chart.

ServerCorrelation

  • JLT-162124 - Add logging when multiple link nodes are registered for the same custom tag.

MessageBrokerAgent

  • JLT-162427 - Redhat 5 fails to load agent on websphere MQ brokers

Mobile

  • JLT-164114 - Deadlock on main thread if iOS Mobile Agent is used with Google Analytics and Google AdMob.

WebserverAgent

  • JLT-156293 - HTML injection in IIS agent would deliver an empty page when lacking network share permission.

6.5.0 Resolved Issues

The 6.5 release contains all changes of:
  • Dynatrace 6.3.6 which in turn includes 6.3.1 - 6.3.5
  • Dynatrace 6.2.11 which in turn includes 6.2.1 - 6.2.10
 Details of changes in 6.3.6

6.3.6 Resolved Issues

6.3.6.1004 Resolved Issues

All resolved issues

WebserverAgent

  • JLT-152509 - UEM: Handle cookies without a value (e.g. Cookie: a; b=c) properly.
  • JLT-154815 - Webserver master agent shutdown unexpectedly deactivates handling of JS agent monitor signals.

Collector

  • JLT-155589 - Fixed potential IllegalAccessErrors when instrumenting Java 8 applications
  • JLT-145615 - A race condition could lead to NullPointerExceptions on the Collector during heavy load and cause agent reconnects.

Server

  • JLT-155478 - Backend server fails to start because of corrupted transaction splitting configuration file
  • JLT-156373 - Fix a problem during session reading caused by changing upper/lower case of system-profile name.

Mobile

  • JLT-156407 - Warnings during build caused by module debugging active for iOS agent build.
  • JLT-155430 - [iOS Mobile ADK] Fixed crash in CPWRCommunicationManager when sending metrics.

UEM

  • JLT-151148 - Basic XHR Detection: When the browser emulates IE8 or IE7, exception "Invalid calling object" occurs during page startup.
  • JLT-147511 - AngularJS module tries to access non-existing config
  • JLT-152865 - Basic XHR Detection: High response times (>180 seconds) are reported when XMLHttpRequest send() throws an exception.
  • JLT-148241 - Allow to map ADK defined applications into user defined applications

Client

  • JLT-155915 - Grouping of User Actions dashlet not applied in reports.
  • JLT-155452 - Hidden buttons in edit custom timeframe filter dialog in linux.
  • JLT-155742 - Error Detection Reporting runs into timeout while getting error details. Changed behaviour to only include details of selected error-rules.
  • JLT-151674 - Db agent: Block explain plan feature for MS SQL Server when query is longer than 8000 (limit in like clause)
  • JLT-149825 - Adapt update check to no longer send the fixes of the currently used update in the update check request.

ServerCorrelation

  • JLT-152970 - MemoryManagement of Server broken due to a wrongly counted internal statistic.

PWH

  • JLT-155518 - Wrong performance warehouse connection status if automatically reconnecting after initial connection error. In this case there is no data written.

6.3.5 Resolved Issues

6.3.5.1050 Resolved Issues

4 critical issues since the last public update

Mobile

  • JLT-152026 - Auto Instrumentation for Android - Fix UI class verify error
    • Impact: Class verifier fails on instrumented UI classes
    • Cause: Perhaps byte code optimization or very large method causing method parameter register be overwritten
    • Solution: Exit callback method now takes no argument

PHPAgent

  • JLT-142124 - Purepaths only show require, include, require_once calls.
    • Impact: No sensors registered.
    • Cause: Agent does not read configuration when blocked path arrives.
    • Solution: Fixed configuration reading.

Client

  • JLT-141106 - Avoid storing user credentials at the client via a server configuration setting.
    • Impact: An attacker may eventually be able to decrypt the data and get the stored user credentials in plain, what could also be LDAP credentials, thus compromising PCI DSS compliance.
    • Cause: The "remember password" option in the client login dialog stores user credentials locally.
    • Solution: Give the administrator the option to disallow storing credentials at the client via an option at the server.

WebUI

  • JLT-151887 - Agent name in chart legend is missing the host name.
    • Impact: No host name appears in the legend.
    • Cause: Wrong use of substring().
    • Solution: Fixed the string concatenation for the legend entry.

80 other issues since the last public update

UEM

  • JLT-152560 - fixed ClassCastException during reporting EuStringNodeAttachment
  • JLT-155444 - Actions time out if jQuery ajax is cancelled via returning "false" in beforeSend callback.
  • JLT-153232 - fix exporting target/source URL in CAS-UEM export
  • JLT-154634 - Fix linking server-side PurePath to W3C resource timing node.
  • JLT-147579 - UEM: Angular: Missing data as Angular sensor copies calls to $log.warn() to the beacon, causing very long beacons.
  • JLT-150769 - UEM: JavaScript Agent: Basic XHR sensor: Error "Invalid calling object" when calling the XMLHttpRequest open() method with an invalid argument.
  • JLT-144521 - When Internet Explorer's advanced "Enable native XMLHTTP support" option is disabled, the dynaTraceMonitor request is not sent.
  • JLT-140307 - PureLytics Stream can now be configured to use multiple connections for streaming.
  • JLT-143441 - Timed Action Support module does not pass context to eval'd setTimeout callbacks
  • JLT-153287 - Fixed evaluation of ending page in page action measures for page actions with cascading load actions.
  • JLT-153272 - [Java Agent] Update ignored filetype list for UEM injection
  • JLT-151844 - High response time reported when an invalid URL causes jQuery $.ajax() to throw an exception.
  • JLT-147392 - NPE during processing mobile action was caused by immediately disposed PurePaths due to overloaded server.
  • JLT-151938 - Unspecified Error from checking xhr.status in aborted beacon signal in IE compat mode
  • JLT-151178 - Ajax request in the form of dojo.xhr.get( ) causes the web page to hang.
  • JLT-149728 - Prevent NPE in UEM correlation while linking sub-action to parent-action and add log message.
  • JLT-151819 - Undefined Error from a.originalXhr.readyState (is null or not an object)
  • JLT-149477 - Incomplete/corrupt resource timings caused corrupt user actions. Resource timings are now validated before processed.

WebUI

  • JLT-153651 - World map does not show data for Republic of Korea

NGINXAgent

  • JLT-155378 - Automatic API breakdown for PHP optimization for Drupal.
  • JLT-154776 - Nginx's agent set proper permissions, when JSON file with offsets is created.
  • JLT-152383 - Fixed crashes in Nginx agent, when POST payload has more than maxSize bytes.

MainframeAgent

  • JLT-144421 - CICS loses the connection to the zRemoteAgent
  • JLT-153366 - zRemoteAgent disconnects when zIIP support is enabled.
  • JLT-151933 - Disabling capture events for mainframe agents causes registration errors.
  • JLT-151815 - zRemoteAgent: Disconnects regularly when zLocalAgent is not connected due to NOOP roundtrip message issue.

Client

  • JLT-147738 - Loss of Fixes dialog is not scrollable and OK or Cancel button cannot be pressed
  • JLT-154070 - Installing an update could cause the Agent Overview's table to report an error.
  • JLT-153346 - Fixpack installation via Start-Center or double click could lead to loss of server connection configurations.
  • JLT-152860 - The listener responsible for the selection was registered to the wrong control only affecting Mac OS X.
  • JLT-147934 - The Update Wizard doesn't properly display buildnumber when update has two-digit revision
  • JLT-144155 - Error dialog 'PurePath not found' shown when drilling into Dynatrace if Client has multiple server connections.
  • JLT-151889 - Changed page fault threshold in HostConfigDialog from 10,000 to 1,000,000

Server

  • JLT-149962 - Fix a problem during session reading where the default LRU size for session-readers for linked paths is too small.
  • JLT-153501 - Fix incorrectly shown Throwable class in ErrorDetection Details for aggregated database nodes.
  • JLT-154589 - PureLytics configuration (when split by application) is reset to default on server startup.
  • JLT-153551 - User action plugin update requires restart of backend server to take effect
  • JLT-151026 - Frontend server: Log Spam: "Cannot find dynamic measures for ..."
  • JLT-153072 - Monitors and monitor-based incidents were displayed with Host Address instead of Host Name.
  • JLT-148826 - Incident e-mail sending doesn't work when Services/Management/Enable Webserver is deactivated.
  • JLT-151524 - Dynamic measures sometimes would not inherit the unit of the parent measure if a custom unit was used.
  • JLT-153122 - Add new GC setting (-XX:G1NewSizePercent=15) to Backend Server
  • JLT-130809 - Logspam in AvailabilityCenter: "The IP address of host X is no longer valid"
  • JLT-152846 - Log storage quota during server startup.
  • JLT-152811 - System profile and server name have been added to Real Time Business Transactions Feed.
  • JLT-151716 - DB Aggregation shows confidential strings
  • JLT-144110 - Missing UserAction PurePaths when drilling down from a serverside Tier in EntryScreen.
  • JLT-151497 - Don't accept licenses with unknown type.
  • JLT-142701 - Obsolete CI REST endpoints to set test metadata still available on HTML system profile management page
  • JLT-143420 - Null pointer check and log message added
  • JLT-145722 - Fix a potential NullPointerException in SessionStorage.

Collector

  • JLT-148771 - Prevent Asp.Net sensor from creating seperate Paths if "BeginRequest" is called in the Asp.Net Pipeline
  • JLT-150545 - Collector Launcher: Self-monitoring Collector does not start as launcher is failing to detect its installation directory on Linux.
  • JLT-152620 - Database Agent: Additional host names mapping not working
  • JLT-151877 - ClassCache cleanup failes due to a broken ClassCache.
  • JLT-153249 - Incorrect tickcounts are reported for CICS/IMS agents after registration. Fixed a zRemoteAgent latency message, due to a missing merge
  • JLT-148349 - Correlation: Path structure problem with WCF Calls in Sharepoint fixed
  • JLT-152110 - Db agent cannot fetch execution plan for sql server if query uses square brackets

WebserverAgent

  • JLT-149183 - Memory leak in JS Agent injection
  • JLT-152748 - WebServerAgent: "Shared memory corruption -- revision unexpectedly decreased" in log
  • JLT-152239 - When Apache redirects requests interally, the root node of the PurePath always shows 200 OK instead of the status code that reaches the browser.
  • JLT-146396 - Webserver Agents bug fix: responses with status code 304 may not contain a message body
  • JLT-149393 - Apache metrics are not getting gathered for Novell Apache
  • JLT-150863 - Apache metrics are not getting gathered for Apache versions >= 2.4.20 due to new scoreboard

Mobile

  • JLT-154600 - rare NullPointerException on agent shutdown

OneAgent

  • JLT-145070 - Agent: Memory Leak in ArrayList::add

ServerRTA

  • JLT-142500 - DB Agent should rely on connection pool node information for mapping to system profile
  • JLT-151288 - CHARTING: Sometimes you'd get gaps in charts starting one hour before the current time and going back for a maximum of one hour.
  • JLT-140109 - Do not book dynamic WebRequest measure when config measure is skipped

DotNETAgent

  • JLT-153906 - PurePaths, containing a large number of aggregated database statements are getting corrupted.

PWH

  • JLT-145983 - Fix no TestResult data when created/imported systemprofile has the same name as a previously deleted systemprofile.

JavaAgent

  • JLT-152926 - Agent does not honor log level settings in the very early phases of initializiation
  • JLT-150911 - Agent startup timeout is longer than "wait" parameter in command line
  • JLT-151855 - JDBC URL in SQLServer datasource not correctly detected

Communication

  • JLT-152595 - Overflow when serializing error detection rules
  • JLT-152299 - Additional DebugFlags to have more options to increase timeouts regarding communication to e.g. mitigate LDAP login problems.

HostAgent

  • JLT-141574 - Bootstrap agent does not use DT_STORAGE for storing its collector peer list.

Plugins

  • JLT-151273 - Windows Performance Monitor measures may be scaled incorrectly on collectors running with Java 8
  • JLT-151293 - URL Monitor Plugin custom HTTP header timer name is only sent for first request.

ServerCorrelation

  • JLT-150781 - Improved correlation completeness check for custom linked rootpaths

6.3.4 Resolved Issues

6.3.4.1034 Resolved Issues

Most important issues since the last public updates

Communication

  • JLT-147809 - Keep custom private keys on the server and do not distribute them to the other components
    • Impact: Potentially keeping private keys on untrustworthy platforms
    • Cause: Every component has to have a private key, thus we distributed custom private keys to them.
    • Solution: Keep the custom private key private to the server by setting the system property com.dynatrace.diagnostics.ssl.allowprivatekeydeployment=false
  • JLT-144134 - A specifically configured proxy may cause the client to use a plain connection instead of SSL/TLS.
    • Impact: A specifically configured proxy may cause the client to use a plain connection instead of SSL/TLS.
    • Cause: Our mechanism to first try with a plain connection, and if successful, not trying with SSL/TLS caused this issue.
    • Solution: Do not try plain connection first, but SSL/TLS.

WebserverAgent

  • JLT-146337 - Nginx Agent: Lack of support for Nginx built using new PIE models.
    • Impact: PIE Nginx binaries built using newest toolchain versions cannot be instrumented
    • Cause: Until now PIE support has covered only two relocation types found in the wild
    • Solution: Recognize and handle two more relocation types observed in the wild

Server

  • JLT-149214 - During server shutdown a NullPointerException is thrown, because after shutdown collector peers are still notified.
    • Impact: Sporadically a NullPointerException is thrown during server shutdown.
    • Cause: Since notification of collector peers is now handled in an ExecutorService, which is set to null after the CollectorCenter shuts down, a NullPointerException is thrown when the collector peers are notified after a server shutdown.
    • Solution: NullPointer check before collector peer update.
  • JLT-144034 - Failed test has influence on corridor calculation and increases volatility
    • Impact: Corridor and volatility of a test was invalid
    • Cause: Failed test executions were included in corridor and volatility calculations
    • Solution: Failed test executions are excluded in corridor and volatility calculations
  • JLT-148031 - When using REST reporting service for XML Test Results dashboard (http://${SERVER_URL}:8020/rest/management/reports/create/dashboard_name?type=xml), obtained XML document doesn't contain any data.
    • Impact: Report was shown without data according to test runs
    • Cause: XML reporter doesn't apply time frame to loaded data
    • Solution: Loads data and apples time frame

PWH

  • JLT-148513 - Aging task attempts to remove dynamic measures still referenced by Test Automation results
    • Impact: Aging task breaks with exception in log if old dynamic measures are still referenced by Test Automation results. Removal transaction is rolled back, so the measures remains unchanged
    • Cause: Aging task tries to remove unused dynamic measures still referenced by Test Automation results when 'Auto purge measures during clean up task' is enabled in PWH Storage Management settings
    • Solution: During the aging task only the unreferenced dynamic measures are removed

Collector

  • JLT-148389 - Db agent shows very high numbers on live view due to skipped delta calculations
    • Impact: Db agent live view slow queries tab
    • Cause: When calculating deltas for live view, if in later query a new sql appeared it was returned as-is without substracting previous values
    • Solution: Queries that appeared only in the second run of the check for slow queries are skipped since we cannot count the delta

Client

  • JLT-147142 - Ensure that updates are also shown for evaluation licenses in the start center
    • Impact: An update notification would be shown but when clicking on it the respective entry in the start center would not be shown.
    • Cause: The update entry was explicitely excluded from the entries in the admin section of the start center, even if the customer was eligible to receive updates.
    • Solution: Allow the entry in the start center also for evaluation licenses as update eligibility is already checked by e-services when checking for updates. Aditionally ignoring the update now also affects the update notification.

All resolved issues

JavaAgent

  • JLT-147512 - Added enforcepci agent option that prevents capturing arguments and creating memory dumps.
  • JLT-150631 - Unix/Solaris: Zone specific memory usage is inaccurate/wrong because reading binary procFS 64bit process data from a 32bit process delivers invalid data.
  • JLT-150088 - If the connection between the agent and collector is lost during the first few classes, the instrumentation might result in a crash of the SUD.
  • JLT-149117 - added cassandra 2.1.13 server support

Communication

  • JLT-150448 - The communication between collector and server can break (session closed with protocol dumps) caused by a race condition in the event buffer sender.
  • JLT-147809 - Keep custom private keys on the server and do not distribute them to the other components
  • JLT-144134 - A specifically configured proxy may cause the client to use a plain connection instead of SSL/TLS.

WebserverAgent

  • JLT-150065 - Apache agent's HTML injection: Proper handling of pre-chunked data as generated by some 3rd party modules.
  • JLT-146337 - Nginx Agent: Lack of support for Nginx built using new PIE models.

Server

  • JLT-136664 - Fix memory problem during session reading when purepaths are linked with themselves.
  • JLT-149658 - REST Interface: can't retrieve specific host incident details
  • JLT-148117 - Added debug logoutput for SUPDT-19002 to get insight to a session-reading problem that causes exceptions like Failed to analyze session with "Illegal path entry type X at position Y"
  • JLT-149777 - Action Plugins receive incorrect threshold information if measure unit was reconfigured.
  • JLT-150145 - Deactivation of usage based volume leads to reset of current UEM reservation usage.
  • JLT-150362 - Fix a memory-leak in Visit-Session management. VisitFileSession and other objects have been leaking in the FileSessionMonitor.
  • JLT-143545 - Security issue: Language pack deployment allowed to download more files than intended.
  • JLT-143612 - Security: system information feature was missing permission checks for file download.
  • JLT-149246 - Agent load balancing tasks is running to frequently. Default settings are changed to: agentBalancingPeriod=1800 (every 30 min), agentBalancingSampleSize=4 (4 x 30 min = 2h moving average), agentBalancingThreshold=50 (in % of current Collector average).
  • JLT-150058 - Fix a problem with postprocessing a 1.4 JVM memory-dump
  • JLT-150064 - The 64-Bit variant of FlagUtils is not working correctly due to the use of a wrong datatype.
  • JLT-147154 - Fixed hostname handling in transaction flow which caused drilldowns to fail.
  • JLT-149214 - During server shutdown a NullPointerException is thrown, because after shutdown collector peers are still notified.
  • JLT-147095 - Improved error logging for Transaction Flow.
  • JLT-148652 - Send only self-monitoring profile to self-monitoring Collector to reduce its memory footprint
  • JLT-143317 - Due to the slow communication between the collector peers, which happens in sequence, the WatchDog decides to restart.
  • JLT-149717 - HTML Reports missed the filter change section.
  • JLT-148772 - .net agents with different versions on a single host require multiple licenses.
  • JLT-144034 - Failed test has influence on corridor calculation and increases volatility
  • JLT-148031 - When using REST reporting service for XML Test Results dashboard (http://${SERVER_URL}:8020/rest/management/reports/create/dashboard_name?type=xml), obtained XML document doesn't contain any data.
  • JLT-145480 - Improved SQL query for retrieving lock information from Oracle Database.
  • JLT-147921 - Fixes an issue where synchronous sub-paths may sometimes not be linked to DTANG paths
  • JLT-147952 - Fixes potentially wrong time calculation with DTANG PurePaths
  • JLT-141776 - Database Hotspots dashlet: Summary execution time min/avg/max calculation incorrect
  • JLT-145458 - Log spam during Support Archive generation
  • JLT-147478 - Drilldown from Incident to Pure Path sometimes shows fewer Pure Paths than expected.
  • JLT-147735 - Fixes a potential NullPointerException with DTANG autosensor attachments
  • JLT-148339 - Incident information handed to user plugins may contain duplicated violation trigger values.
  • JLT-144370 - Missing problem report after data performance warehouse issue.
  • JLT-144472 - Log spam after migration from 6.1: "Unknown native agent library found in C:\Program Files\dynaTrace\Dynatrace 6.3\server\lib\agentres-6.1.0.8433.jar"
  • JLT-147515 - Server: NullPointerException in MobileWorkloadDataProvider.getFirst
  • JLT-148759 - REST reports HTTP error 500 with NoClassDefFoundException because of missing OSGi bundle requirement definition.
  • JLT-145459 - Bug in processing of JMX measurements causes unnecessary commands being sent from server to agent.
  • JLT-143551 - Security: Missing permission checks for plugin bundle management allowed non-privileged users to upload files.

PWH

  • JLT-148513 - Aging task attempts to remove dynamic measures still referenced by Test Automation results
  • JLT-146764 - Omit migration of orphaned Test Automation data, which can lead to foreign key violation
  • JLT-147421 - Implement DebugFlags ciDataMigration* to improve performance of Test Automation data migration by optional commit statements (flags not usable for PostgreSQL)
  • JLT-144185 - Make batch size configurable for percentile insert sql statement
  • JLT-146771 - Log more information when performance warehouse data migration fails.
  • JLT-142628 - PWH: ORA-01461 when inserting incident with long system profile name string
  • JLT-148887 - PWH: Upgrade Oracle driver from 12.1.0.1.0 to 12.1.0.2.0
  • JLT-147950 - no retries of performance warehouse connect when password is empty

Collector

  • JLT-149182 - If a collector authentication string is configured, it is lost when changing collector configuration via UI.
  • JLT-147578 - jrockit might freeze on StackOverflowError when the exception sensor is placed.
  • JLT-141935 - Db agent: show window with progress bar when requesting sql execution plan
  • JLT-142666 - Sql server db agent is missing sql execution plan date on sql execution plan dialog
  • JLT-148389 - Db agent shows very high numbers on live view due to skipped delta calculations
  • JLT-148925 - Malformed PurePath for HTTP requests when 6.1 agent connects to 6.3 collector
  • JLT-148510 - Global Agent time is not initialized properly on subAgent connect, and can be off for up to 10 seconds.

Client

  • JLT-149948 - Db agent configuration: on Mac OSX username/password are cleared after clicking test connection
  • JLT-150874 - Importing a newer license with an unknown type breaks licensing UI.
  • JLT-147197 - certificate wizard: add support for PKCS#8 decoded key pair
  • JLT-148220 - Chart color changes from default measure color after adding to chart
  • JLT-148945 - Monitoring Dashboard no longer automatically activated, when the Server disconnects
  • JLT-149556 - Display issue with globally overridden properties of incident actions.
  • JLT-150060 - Sysinfo dashlet stays empty or shows incomplete information.
  • JLT-148033 - Db agent configuration: option to add host names mapping in debug UI
  • JLT-148296 - Drilldown from End User BT splittings in Dynamic Measure Matrix dashlet failed due to invalid filter settings.
  • JLT-149373 - Unable to analyze memory snapshot triggerd by OOM because the VM did not provide a OOM description string.
  • JLT-144270 - Process Details View did not show GC Casesed Suspension Time correctly in the Chart
  • JLT-149177 - Communication problem (network disconnect, ...) during "Confirm Incidents" can cause unhandled NullPointerException.
  • JLT-144613 - Fixed problem with sorting Session table by SessionID in Database Live View for Microsoft SQL Server.
  • JLT-147142 - Ensure that updates are also shown for evaluation licenses in the start center
  • JLT-148284 - Fix that no entries are shown in the admin section of the start center, in case the update entry was ignored prior to installing the update.
  • JLT-149133 - Host dashlet generates invalid and incomplete XML reports.
  • JLT-148620 - Ensures that the Monitoring Dashboard is not part of the Kiosk-Mode Dashboards.

MainframeAgent

  • JLT-150437 - Fix the elapsed time in the CICS/IMS agent by roundtripping the noop message.
  • JLT-149091 - CICS/IMS Elapsed times are inaccurate.

UEM

  • JLT-150554 - DynaTraceMonitor requests block pageunloads due to synchronous XMLHttpRequests. Providing a "forceAsync" flag to force the agent to send DynaTraceMonitor requests asynchronously via custom configuration property "fa=1".
  • JLT-146341 - UEM: In the Java-based app server agent, invalid dtCookie content was logged as a Java IllegalArgumentException with a stack trace, making it seem to be a fatal problem.
  • JLT-149329 - JavaScript stack overflow error, when the bandwidth sensor is enabled.
  • JLT-147555 - fixed NPE when changing resource state for CDN Content Count measure
  • JLT-150018 - UEM: JavaScript agent can't detect it's features and no enabled modules are active due to non-working script-tag detection.
  • JLT-147187 - JavaScript Agent: Basic XHR sensor: Error "Invalid calling object" or error "Cannot read property 'apply' of undefined" when calling methods on the XHR object.
  • JLT-142532 - Perceived render time module reports incorrect timings if no images are present or no load action is fired on a website.
  • JLT-146972 - UEM: UserAction name of imported Session is not complete and displays a Dash.
  • JLT-144973 - Ignore empty dtCookie values on Java agent.

InstallerAndBuild

  • JLT-150659 - Included external bundles into update content description to prevent log spam.

NGINXAgent

  • JLT-149810 - Agent bootstrapper can cause nginx to crash at startup.

ServerCorrelation

  • JLT-135603 - Symptom: Log spam: Recieiving many maximum linked path depth of 500 reached errors. Solution: Reduce log interval but affected PurePaths will be shown.
  • JLT-148864 - Correlation blocked synchronous by communication to collector

Mobile

  • JLT-149340 - Auto Instrumentation for Android - update 3rd party tools to the latest
  • JLT-132688 - Added support for iOS 9.x bitcode
  • JLT-144147 - Support for extracting line numbers from iOS symbol files (dSYMs).
  • JLT-145279 - Mobile ADK crashes when addTarget is call while target is being disposed. There is a bug in iOS prior to 9.0 which causes viewDidLoad to get called if accessing the view during dealloc.
  • JLT-146760 - Added support for Xcode 7.3 when using the Xcode Plugin

DotNETAgent

  • JLT-128314 - The WCF sensor is now able to reuse OutgoingMessageProperties for response tagging. No more ArgumentException in PurePath when a WCF service uses OutgoingMessageProperties
  • JLT-144412 - The WCF sensor is now able to reuse OutgoingMessageProperties for response tagging. No more ArgumentException in PurePath when a WCF service uses OutgoingMessageProperties

6.3.3 Resolved Issues

Most important issues

  • JLT-148860 - Backend Server Process restarted by watchdog.

    Impact: Backend Server Process restarts.
    Cause: The Backend Server Process is restarted by the watchdog since a ServerTimerService-Thread does not get any work for longer than the watchdog timeout.
    Solution: Use watchdog per task instead of per thread.

  • JLT-140137 - Webserver Agent: Potential crash due to a zlib bug

    Impact: Webserver Agent crashes because of an access violation
    Cause: We're using the 3rd party zlib component to compress and uncompress request/response data. In some certain (and probably rare) cases it might happen
        that the webserver agents run into a zlib bug where it tries to read more bytes than available. We were not able to reproduce that case in the lab.
    Solution: We can't fix that bug directly, so we implemented a workaround: we allocate 8 bytes more than needed. Since zlib always reads 8 bytes at once that
        workaround should fix the access violation crash.

  • JLT-146053 - Potential Apache 2.4 worker crash during startup with mod_deflate and mod_filter

    Impact: Simultaneous requests after startup can lead to concurrent filter registration and potentially to crashes.
    Cause: Non-threadsafe registration of injection filter during request processing.
    Solution: Registering our injection filter twice with different filter types and only adding it to filter chain during request processing.

  •  JLT-145720 - UEM: Fixed vulnerabilities in the handling of invalid requests in server-side agents.

    Impact: The agent would cause termination of the web server, with an uncaught exception.
    Cause: A malformed dtCookie value could cause the web server agent to exceed the bounds of the string.
    Solution: The dtCookie processing logic has been corrected.  Invalid values are now safely rejected.

  •  JLT-147673 - Backend Server Process restarted by watchdog.

    Impact: Backend Server Process restarts.
    Cause: The Backend Server Process is restarted by the watchdog since a ServerTimerService-Thread does not get any work for longer than the watchdog timeout.
    Solution: By default only 1 thread is used for this now. With this update, the number of Threads for ServerTimerService is adjustable.

  •  JLT-145102 - WebUI: Dashboard would not refresh automatically
      Impact: No changes would be shown on dashboards, manual refresh was required.
      Cause: Promises can only be resolved once, thus after initial refresh no updates would be published.
      Solution: Reenable cyclic updates
  •  JLT-143502 - Drilldowns from Transaction Flow to DB Agent Health dashlet aren't working.

    Impact: Drilldowns from Transation Flow not always working.
    Cause: DB Agents were not mapped using status information from AvailabilityCenter in Transation Flow.
    Solution: Use AvailabilityCenter for DB Agent mapping in Transation Flow.

  •  JLT-146496 - Agent hinders startup of managed Weblogic Application Server 12.2.1

    Impact: The managed server instance cannot communicate with the admin server, causing an immediate shutdown
    Cause: WLS 12.2.1 comes with new T3 remoting classes which are not instrumented correctly
    Solution: With this fix WLS 12.2.1 is instrumented correctly without breaking the T3 protocol

  •  JLT-144282 - UEM: Polling requests cause AngularJs actions to time out

    Impact: Actions may time out and thus appear absurdly long
    Cause: Background requests occurring at the time of other AngularJs XHRs disrupt internal callback counters
    Solution: Have more checks and ensure the counters are reset if deferred xhr actions time out

  •  JLT-145873 - Visit User Actions display the wrong URI in the name

    Impact: User actions are displayed like 'click on "someBtn" on /destination' when it should be 'click on "someBtn" on /source'
    Cause: Source/Target URL implementation in 6.3. Missed a place where URL is still treated as the source URL when it is actually the target.
    Solution: Use the sourceURL instead of URL parameter when getting the prettyName for the visit's user action table.

  •  JLT-145743 - UEM: Meta tag config can include characters which could break a page.

    Impact: Javascript Agent metatag configuration can break web page.
    Cause: Metatag configuration can contain HTML special characters which are interpreted as normal page content by the browser, hence destroying HTML tags or attributes.
    Solution: Special characters are serialized to non-vulnerable string sequences during page rendering.

  • JLT-148429 - WebUI: Changing measure splitting selection affects other tiles using the same measure

    Impact: Changing a measure splitting selection in one tile affects other tiles using the same measure.
    Cause: Attempt to fix issue JLT-144538.
    Solution: Reverted fix for JLT-144538.

  • JLT-142541 - Mobile ADK: iOS application has the potential to crash when calling [UIDevice setBatteryMonitoringEnabled:] either in the app or from 3rd party frameworks. This can happen because UIKit is not thread safe.

    Impact: Instrumented application will crash if the application calls [UIDevice setBatteryMonitoringEnabled:] at the same time as the Mobile ADK
    Cause: [UIDevice setBatteryMonitoringEnabled:] is not thread safe
    Solution: Made calls to [UIDevice setBatteryMonitoringEnabled:] thread safe

  • JLT-146281 - Mobile ADK: ADK calls wrong hooked method when super lifecycle method is called directly by an app outside of the lifecycle view call path

    Impact: Instrumented application may behave unpredictable.
    Cause: ADK always assumed that it would be called from lifecycle event, not via a super call.
    Solution: Fixed code in ADK to know if called from true lifecycle or from a super call.

  •  JLT-142934 - Mobile ADK: Porting JLT-140965 Auto-instrument cookie manager to preserve dtADK cookie

    Impact: Event generated by the javascript and mobile agents are not correlated into the same visit
    Cause: Customer delete dtAdk and dtAdkTag cookies in their javascripts causing split visits
    Solution: Auto instrumentor to detect cookie deletion and restore the cookies

All resolved issues

WebserverAgent

  •  JLT-143908 - Updated ignored filetype list for JavaScript Agent injection
  •  JLT-140137 - Webserver Agent: fix crashes due to a zlib bug
  •  JLT-146585 - WSAgent: Correct version number handling, support two-digit revisions in JS agent requests
  •  JLT-146053 - Potential Apache 2.4 worker crash during startup with mod_deflate and mod_filter
  •  JLT-141390 - Apache agent: ETag headers that are removed from the response by mod_headers are restored again by the agent when UEM is enabled.
  •  JLT-141910 - Apache agent: reduce the likelihood of a newly-spawned worker process handling the first few requests without an agent config due to SHM file spinlock contention (the most visible consequence being UEM functionality sporadically not kicking in).

MainframeAgent

  •  JLT-149010 - Connection timeout between zDC and zRemoteAgent
  •  JLT-148345 - zRemoteAgent hangs on a handshake request from the zLocalAgent, if network is unstable
  •  JLT-148113 - zRemoteAgent crash causing CICS/IMS disconnects
  •  JLT-144920 - Possible CPU spin in zLocalAgent, when zRemoteAgent is disconnected, and zIIP support not enabled
  •  JLT-147876 - Possible CPU spin in zLocalAgent, when zRemoteAgent is disconnected, and zIIP support not enabled
  •  JLT-145557 - zLocalAgent deadlock, causing SMO/TxB buffers to overflow and backup
  •  JLT-145555 - Change a failing subagent license message in the agent logs to WARNING from INFO
  •  JLT-145084 - zLocal Agent log files don't appear in the system information dashlet

Server

  •  JLT-148860 - Backend Server Process restarted by watchdog.
  •  JLT-148499 - NullPointerException on agent deregistration after agent has been load balanced to a different collector
  •  JLT-148573 - Server might cancel connection setup to collector where fixpack synchronization lasts longer than 2min
  •  JLT-148400 - In scenarios with 10+ real time worker threads, dtserver is restarted due to watch dog timeouts caused by inefficient subscription processing.
  •  JLT-148494 - Server in endless restart loop caused by commented GC setting in dtserver.ini
  •  JLT-148235 - Browser timeline not showing snapshots due to outdated mshtml.dll offsets
  •  JLT-148104 - Improve logging in case Global Agent Time problem is detected.
  •  JLT-147967 - Dynatrace storing only 1 hour data in both session storage as well as live monitoring
  •  JLT-143193 - Collector: Server considers Agent offline because it assumes that the Agent is connected to different Collector
  •  JLT-147559 - Exceptions during session-reading and not data available from PureLytics when using CICS agents that generate empty PurePaths.
  •  JLT-141799 - Introduce SessionSizeTracker for periodically checking real session sizes on disk and correcting in-memory sizes
  •  JLT-145243 - Correlation Engine: Circular linked purepaths caused by non-unique custom tags and a race condition.
  •  JLT-145350 - Race condition between collector/server time synchronization and collector/server agent registration. Some agents might not reflect the collector/server time difference correctly
  •  JLT-147673 - Backend Server Process restarted by watchdog.
  •  JLT-144539 - dtserver.ini file has wrong GC settings after rollback with version 6.3.0.1282 (RC3) or smaller
  •  JLT-143502 - Drilldowns from Transaction Flow to DB Agent Health dashlet aren't working.
  •  JLT-144010 - Slow PWH connection can lead to memory leaks
  •  JLT-146456 - Action plugins may rarely receive incomplete incident information.
  •  JLT-146214 - Exceptions during shutdown
  •  JLT-144166 - PureLytics missing data due to UncategorizedRepositoryException (transaction aborted) after re-creating renamed system profile.
  •  JLT-146359 - Ping Watchdog more frequently in DiskUsageCheckTask. In some cases the time between pings is currently too long which results in termination of runtime.
  •  JLT-143869 - Improved support archive information about virtual agent time.
  •  JLT-144011 - Browser Diagnostics: Update for native instrumentation data of Internet Explorer Rendering Sensor
  •  JLT-144105 - Allow '=' character to be included in HTTP header values (NA and TN) for WebAPI test names.
  •  JLT-144265 - Incident end date not set after closing in IncidentRuleEngine.
  •  JLT-143867 - DB Agent Guardrail - forbid creating too many DB agents
  •  JLT-141710 - Licensing: Improve IIS counting for hourly agent usage log and measure.
  •  JLT-142531 - Incidents: When confirming an incident based on a host performance measure, the measure becomes renamed and unusable.
  •  JLT-142655 - Logging: SQL Spy logs should only appear in Repository.log
  •  JLT-142797 - Incident Rules not honoring changed Measure Thresholds.
  •  JLT-143185 - Improved logging of licensing problems.
  •  JLT-143282 - Test Automation: Invalidated test runs might disturb corridor calculation
  •  JLT-145750 - PureLytics: Create new readstate file in case it is corrupt.
  •  JLT-140769 - Charting: When charting >= last 14 days with a 1d resolution, you'll get wrong values for the current day
  •  JLT-145498 - Removed DB Agents should not be included in the Overview list
  •  JLT-146679 - Fix master Agent (ZRemoteAgent) crash during subAgent recovery.
  •  JLT-143469 - "Host Incidents" are not stored in continuous recording session
  •  JLT-143474 - Availability threshold in infrastructure overview not removed
  •  JLT-143856 - Host Monitoring: File system and nic exclusions do not apply for newly created system profiles

Client

  •  JLT-147406 - The listener responsible for the selection was registered to the wrong control only affecting Mac OS X.
  •  JLT-146124 - Non-admin: No data or "Insufficient Permissions" with Host overview and Database Dashlets
  •  JLT-147099 - Admin user is not able to modify some user roles.
  •  JLT-147681 - Sysinfo dashlet stays empty.
  •  JLT-145818 - Some regex patterns for method sensor rule could not be entered correctly.
  •  JLT-143302 - EntryScreen automatically selects an invalid session and reports an error.
  •  JLT-141645 - Filter favorites are not preserved between invocations of the Client.
  •  JLT-144942 - An update notification was shown but the update did not appear in the start center in case the update was already uploaded to the server.
  •  JLT-145439 - Failed Transaction drill-down opens ALL purepaths (no filter) for selected timeframe
  •  JLT-146275 - Location for creating a web dashboard pushed to the browser from the rich client was not using the specified web server host.
  •  JLT-144469 - Count aggregation not available for all measures when used in incident configuration.
  •  JLT-144024 - Certificate deployment wizard: corrected wording
  •  JLT-145203 - Start center: corrected wording
  •  JLT-144396 - Location for creating a web dashboard was pushed wrong to the browser from the rich client.
  •  JLT-144921 - Warning message "A problem occurred while analyzing 'Entry Screen'." doesn't disappear.
  •  JLT-146194 - In some circumstances the Transactionflow incorrectly shows container icons instead of virtualization or cloud icons.
  •  JLT-143485 - When closing the HostDetails dashlet and a refresh request is running, it might cause the client to report bad errors.
  •  JLT-145429 - Configuration screen of measure "Page Actions - Metadata" is not displayed

UEM

  •  JLT-148129 - Basic XHR sensor: When Content-Security-Policy is enabled, the use of (new Function("")) is flagged.
  •  JLT-142671 - Improve endVisit handling in order to let late incoming actions be assigned to a visit, which was already ended via endVisit event.
  •  JLT-148358 - UEM: Metadata Capturing Does Not Remove Capture Expression
  •  JLT-148361 - UEM: Metadata Capturing Leads To Exception in JS Agent
  •  JLT-147980 - Unexpected results on IE7 when reusing a cached XMLHttpRequest object for a synchronous request.
  •  JLT-148245 - NullPointerException in RootExecPathInfoForUemCorrelation.getMeasurments
  •  JLT-144641 - Correct version number handling for JS agent requests, in order to allow 2 digit revisions.
  •  JLT-145135 - Active X Module causes out of memory exceptions when browsing for hours on the same page on IE 7 and 8.
  •  JLT-145720 - UEM: Fixed vulnerabilities in the handling of invalid requests in server-side agents.
  •  JLT-143280 - Third party times provided by JavaScript agent are validated and dropped if they seem too high.
  •  JLT-145609 - Provide capture of third party resources contained within iframes.
  •  JLT-146131 - Report generated from User Actions Health or Functional Health dashlet did not contain all data.
  •  JLT-144282 - UEM: Polling requests cause AngularJs actions to time out
  •  JLT-142436 - Provide possibility to exclude specific requests from being tracked by the JavaScript agent via a regular expression.
  •  JLT-143130 - Handle exception in CacheHookkingRequestWrapper.getDateHeader in order to return -1 if "If-Modified-Since" header should be swallowed
  •  JLT-144211 - Adding multiple error listeners to jQuery ajax settings results in exceptions and non-executed callbacks.
  •  JLT-144416 - ActiveXObject module causes responseText not being updated when object is reused.
  •  JLT-145873 - Visit User Actions display the wrong URI in the name
  •  JLT-140758 - NullPointerException during "Stop UEM Debugging"
  •  JLT-145273 - No city values for Spain country on WorldMap. Caused wrong region handling of data provided by new maxmind database used since 6.3
  •  JLT-145316 - UEM business transactions with server-side measurements are failing because the measurements are reset on server-side paths during orphaned web request handling
  •  JLT-145743 - [JS Agent] Meta tag config can include characters which could break a page.
  •  JLT-143892 - Mobile ADK Application mapping problem: Webserver Agents were sending the full monitor request path instead of the monitor signal name to the Mobile ADK.

WebUI

  •  JLT-148429 - WebUI: fix that changing measure splitting selection affects other tiles using the same measure
  •  JLT-146348 - Bad default colors for line and bar charts
  •  JLT-146400 - Changing a BT List tile setting overrides the result-measure setting from another BT List tile on the same dashboard (occurred only if another BT List Tiles has been edited before).
  •  JLT-146844 - Add "autocomplete=off" to Login form for PCI compliance.
  •  JLT-141634 - When drilling into certain regions the world map is cut off and the "Analyze visits" looks misplaced.
  •  JLT-145438 - Default resolution for pie and meter charts caused inconsistent values between Rich Client and Web Dashboards.
  •  JLT-144538 - Improve handling of switching between tile types in the tile configuration (issue not fully fixed).
  •  JLT-145223 - When dashboards from 6.1 which were created using a system with an encoding different to UTF-8 and JSON files with special characters are imported to 6.3, the loading procedure of the dashboard file fails.
  •  JLT-138562 - Add the "Copy tile" action to dashboards.
  •  JLT-140401 - Allow more columns in a dashboards to better support high-resolution screens.
  •  JLT-140535 - Show charts for synthetic and robot visits on the Omni channel page.
  •  JLT-140828 - World map automatically zooms into regions if only one continent or country contains data.
  •  JLT-141146 - Add the "Analyze visits" action to the Worldmap, which links to the pre-filtered User satisfaction page.

DotNETAgent

  •  JLT-125843 - Added debug flag for the .NET agent (debugHttpTaggingEnableTraceTagCleanAfterThreadSwitchDotnet) to enable handling of thread switched during an incoming HTTP request.

Mobile

  •  JLT-142541 - Mobile ADK: iOS application has the potential to crash when calling [UIDevice setBatteryMonitoringEnabled:] either in the app or from 3rd party frameworks. This can happen because UIKit is not thread safe.
  •  JLT-146281 - Mobile ADK: ADK calls wrong hooked method when super lifecycle method is called directly by an app outside of the lifecycle view call path
  •  JLT-130233 - Mobile ADK: Android auto-instrumentation overrides final lifecycle methods when ListActivity and ExpandableListActivity are not visited
  •  JLT-142934 - Mobile ADK: Porting JLT-140965 Auto-instrument cookie manager to preserve dtADK cookie
  •  JLT-145610 - Mobile ADK: Android auto-instrumentation prevents app start due to IllegalArgumentException
  •  JLT-145994 - Mobile ADK: Android auto instrumented app sends no data due to too many strings and DEX not throwing exception
  •  JLT-146741 - Improve test stability (language tests in RuxitProtocolTest)

ServerCorrelation

  •  JLT-139487 - Improve Supportability by changing the content of Global Agent Time Delta and Virtual Agent Time Delta and improve logging in case of Global Agent Time problems.
  •  JLT-145330 - Fixes an issue where time calculation might be wrong for some DTANG PurePaths
  •  JLT-143346 - ExecPathNode.tryHideNode() is not dev/debugging friendly

Communication

  •  JLT-137585 - Improved robustness of server/collector sessions
  •  JLT-142526 - The DynatraceHttpClient may cause log spam when used for DC RUM.

Collector

  •  JLT-147375 - Some java 8 classes can not be instrumented because of a ClassCastException during instrumentation.
  •  JLT-146496 - Agent hinders startup of managed Weblogic Application Server 12.2.1
  •  JLT-145002 - Fixed potential IllegalAccessError with Java 8 and newinvokespecial.
  •  JLT-145985 - Workaround for a Java 8 memory leak which is triggered by instrumentation.
  •  JLT-144310 - Collector and backend server log: Write constant length asterisks to not reveal password length for db agent
  •  JLT-144111 - On deinstallation of some plugins it may be possible that the collector deployment gets corrupted.
  •  JLT-145910 - Collector-Server communication breaks because of a race condition during serialization.
  •  JLT-145998 - Fixed potential IllegalAccessError introduced with the java 8 pretransformation debug flag.
  •  JLT-145423 - High instrumented application memory usage in Java 8 (now revert to 6.2 instrumentation behavior and add debug flag to override)
  •  JLT-144401 - MongoDB sensor causes java.lang.VerifyError with MongoDB java driver 3.1.0 or higher

JSAgent

  •  JLT-137130 - Authentication sent via the XMLHttpRequest object is incorrectly handled or is blocked by the browser. JavaScript event handlers on the XHR.upload object are not invoked.

JavaAgent

  •  JLT-145949 - Adding support for Tibco Business Works SE 5.9 (unobfuscated code)
  •  JLT-135047 - JMX measures based on coherence cache MBeans do not work after application restart due to volatile coherence node ids
  •  JLT-138619 - Added guardmethods agent option.
  •  JLT-146584 - Fixed debug logs with debugClassLoadClassInformationNative, which would log garbage on z/OS due to wrong encoding
  •  JLT-146174 - Changed MBeanServer management caused not working PMI measures on some WebSphere versions (e.g. 8.5.5)
  •  JLT-143661 - Excluding class org.jboss.as.jmx.MBeanServerAuditLogRecordFormatter from instrumentation as it causes CPU overhead
  •  JLT-146472 - Fixing a possible NullPointerException for the Mule Tagging Sensor

InstallerAndBuild

  •  JLT-147170 - Webserver agent installer on Solaris x86 (32/64): Add all supported webserver agents

PWH

  •  JLT-144077 - Improve exception handling when Performance Warehouse was disconnected

ServerRTA

  •  JLT-146471 - Percentiles: Wrong percentile values for measures that have more than one value for a purepath
  •  JLT-145850 - RTA statistics will be written to correlation log only for the last hour to avoid DB timeout

HostAgent

  •  JLT-146590 - Linux Memory Used/Memory Useable metrics are not accounting for SReclaimable/SwapCached

 

6.3.2 Resolved Issues

Most important issues

Performance Warehouse

  • JLT-146707 - PWH migration: FlywayJdbcMigration swallows exceptions in 6.3.1, can lead to unnoticed data loss

  • JLT-145691 - Disable PWH access to Test Automation data during migration

6.3.1 Resolved Issues

Most important issues

Java Agent

  • JLT-145158 - Memory leak in applications running in Java 8
    • Impact: High host memory usage in instrumented application running in Java 8 JRE
    • Cause: Specific instrumentation behavior in combination with assumed JVM bug JI-9032177
    • Solution: Use previous 6.2 behavior
  • JLT-145423 - High instrumented application memory usage in Java 8 (now revert to 6.2 instrumentation behavior and add debug flag to override)

Server

  • JLT-145026 - Add parameter in dtserver.ini as workaround for Oracle JVM crash.
    • Impact: Backend server crash with Oracle JVMs
    • Cause: Oracle JVM bug JDK-8020750
    • Solution: Disable Just-in-time compilation of problematic code parts

Performance Warehouse

  • JLT-145092 - Losing a connection to a PWH during a DB schema migration can lead to an inconsistent state
    • Impact: Missing data and misleading "Schema is missing or outdated message" and related repository log entries
    • Cause: Incorrect handling of connection abort during PWH migration
    • Solution: Correct and continue aborted migration of old data

All resolved issues

Server

  • JLT-145026 - Add parameter in dtserver.ini as workaround for Oracle JVM crash.
  • JLT-143544 - Security: Existing user could get access to other user's password hashes and community email and encrypted passwords
  • JLT-139597 - Repository logging: log spam "Successfully started derby on port X" when connection to derby doesn't work
  • JLT-110325 - Combined changes to update to latest available version.
  • JLT-145329 - Fixed potential PurePath corruption for paths sent by Node.js agents.

ServerCorrelation

  • JLT-145330 - Time calculation might be wrong for some DTANG PurePaths

Performance Warehouse

  • JLT-145092 - Losing a connection to a PWH during a DB schema migration can lead to an inconsistent state
  • JLT-145318 - Misleading error message when performance warehouse creation/migration fails.

Client

  • JLT-145331 - 'Cannot format given Object as a Date' found in client log, if servers communication certificate expires within 3 months
  • JLT-144241 - When switching dashboards the 'Client Errors' dashlet leaks memory and resource handles. Especially Clients running in kiosk mode are affected.
  • JLT-144244 - When switching dashboards the dashlets 'Agent Breakdown', 'Components', 'Database', 'Database Hotspots', 'Entry Points', 'Exceptions', 'Logging', 'Messaging', 'Methods', 'Mobile Workload', 'Naming Services', 'Remoting', 'Tagged Web Requests', 'Web Requests' and Web Services leak memory and resource handles. Especially Clients running in kiosk mode are affected.
  • JLT-144280 - When switching to or from 'Infrastructure Overview' the Client leaks memory and resource handles. Especially Clients running in kiosk mode are affected.
  • JLT-144286 - When switching dashboards the dashlets 'Database Instance', 'Database Instances' and 'Database Live View' leak memory and resource handles. Especially Clients running in kiosk mode are affected.
  • JLT-144287 - When switching dashboards the 'Database Instances' dashlet leaks memory and resource handles. Especially Clients running in kiosk mode are affected.
  • JLT-144504 - When switching dashboards the 'Entry Screen' dashlet leaks memory and resource handles. Especially Clients running in kiosk mode are affected.

UEM

  • JLT-145033 - Cyclic redirects can cause a StackOverflow in UEM correlation. A recursion depth limitation was added to prevent this.
  • JLT-144506 - W3C timings for e.g. about.blank caused an MalformedURLException in PurePathNodeAnalyzer during analysing an user action. 

Collector

  • JLT-144401 - MongoDB sensor causes java.lang.VerifyError with MongoDB java driver 3.1.0 or higher

.NET Agent

  • JLT-145656 - .NET Agent: with unsupported v.1.1 CLRs: Application crash during initialization

MainframeAgent

  • JLT-138514 - If the zRemoteAgent is bounced with zIIP enabled, the zLocalAgent doesn't always reconnect properly, leaving CICS/IMS subagent disconnected.
  • JLT-141878 - Connectivity issues with the zRemoteAgent and the CICS/IMS regions
  • JLT-142401 - The zRemoteAgent and zLocalAgent experience socket connection errors.
  • JLT-142582 - CICS subagents don't initialize in a timely fashion when the zDC or zRemoteAgent are restarted
  • JLT-144959 - zRemoteAgent connectivity drops when a collector fail-over is initiated.
  • JLT-145632 - zRemoteAgent crashes, causing loss of connectivity and agent disablement.

JavaAgent

  • JLT-145998 Java Agent: Cassandra Server 3.0.3 fails to start with IllegalAccessError (follow up from JLT-145158 and JLT-145423)
  • JLT-144562 - Agent: High memory usage in OptimizedStack
  • JLT-140929 - Quasi parallel start-up of agents with same agent name can lead to agent log warning "Exception storing collector peer list: Access is denied."
  • JLT-144488 - Enabling a specific debug flag could result in a crash on Java 8 VMs.

 Details of changes in 6.2.11

6.2.11 Resolved Issues

6.2.11.1005 Resolved Issues

Server

  • JLT-156373 - Fix a problem during session reading caused by changing upper/lower case of system-profile name.
  • JLT-131006 - Fix a bug during Thread dump creation error handling.
  • JLT-155740 - Improve logging in case of global agent time problems, only log affected agents.

UEM

  • JLT-153947 - Performing a UEM Database update through the Start Center failed to update the associated files.

Client

  • JLT-155742 - Error Detection Reporting runs into timeout while getting error details. Changed behaviour to only include details of selected error-rules.
  • JLT-147738 - Loss of Fixes dialog is not scrollable and OK or Cancel buttons cannot be pressed

PWH

  • JLT-155518 - Wrong performance warehouse connection status if automatically reconnecting after initial connection error. In this case there is no data written.

6.2.10 Resolved Issues

All resolved issues since 6.2.9

Webserver Agent

  • JLT-155087 - Additional logging for troubleshooting UDP-related subagent registration problems.
  • JLT-149183 - Memory leak in JS Agent injection.
  • JLT-144535 - Webserver/JS agent issue with splitted visits due to dtCookie=null

Server

  • JLT-153501 - Fix incorrectly shown Throwable class in ErrorDetection Details for aggregated database nodes.
  • JLT-142453 - Minor improvements for gc behaviour of backend-server process.
  • JLT-154589 - PureLytics configuration (when split by application) is reset to default on server startup.
  • JLT-153551 - User action plugin update requires restart of backend server to take effect.
  • JLT-110325 - Combined fixes to update to latest available version.

UEM

  • JLT-147579 - UEM: Angular: Missing data as Angular sensor copies calls to $log.warn() to the beacon, causing very long beacons.
  • JLT-143441 - Timed Action Support module does not pass context to eval'd setTimeout callbacks

NGINXAgent

  • JLT-154776 - Nginx's agent set proper permissions, when JSON file with offsets is created.

Client

  • JLT-142050 - Dashlets would get cut off if the client size was insufficient to display all dashlets of dashboard. This fix adds the option to the dashboard configuration to show scrollbars in that case.

JavaAgent

  • JLT-150088 - If the connection between the agent and collector is lost during the first few classes, the instrumentation might result in a crash of the SUD.

  • JLT-153272 - Update ignored filetype list for UEM injection.

OneAgent

  • JLT-145070 - Agent: Memory Leak in ArrayList::add

PHPAgent

  • JLT-142124 - Purepaths only show require, include, require_once calls.
  • JLT-145060 - Duplicate of JLT-138873.

Miscellaneous

  • JLT-153072 - Monitors and monitor-based incidents are shown using host address instead of host name.
  • JLT-145983 - Fix no TestResult data when created/imported systemprofile has the same name as a previously deleted systemprofile.
  • JLT-150545 - Collector Launcher: Self-monitoring Collector does not start as launcher is failing to detect its installation directory on Linux
  • JLT-153346 - Fixpack installation via Start-Center or double click could lead to loss of server connection configurations.
  • JLT-142124 - Purepaths only show require, include, require_once calls.

 


6.2.9 Resolved Issues

All resolved issues since 6.2.8

Mainframe

  • JLT-153366 - zRemoteAgent disconnects when zIIP support is enabled.
  • JLT-153249 - Incorrect tickcounts are reported for CICS/IMS subagents immediately after registration.

Client

  • JLT-151524 - Client: Dynamic splittings would not inherit the parent unit if a custom unit was set on the parent in some instances.
  • JLT-147934 - The Update Wizard doesn't properly display buildnumber when update has two-digit revision
  • JLT-144155 - Client: Error dialog 'PurePath not found' shown when drilling into Dynatrace if Client has multiple server connections.
  • JLT-151889 - Changed page fault threshold in Infrastructure/HostConfigurationDialog from 10,000 to 1,000,000
  • JLT-151716 - DB Aggregation shows confidential strings

Agent

  • JLT-152748 - WebServerAgent: "Shared memory corruption -- revision unexpectedly decreased" in log
  • JLT-146396 - Webserver Agents bug fix: responses with status code 304 may not contain a message body
  • JLT-150863 - Apache metrics are not getting gathered for Apache versions >= 2.4.20 due to new scoreboard
  • JLT-149393 - Apache metrics are not getting gathered for Novell Apache
  • JLT-144233 - PHP agent causing Access Violation error in php-cgi with Oracle Sensor enabled
  • JLT-141574 - Bootstrap agent does not use DT_STORAGE for storing its collector peer list (requires new installer)

Collector

  • JLT-151877 - ClassCache cleanup fails when the bytecode of a class cannot be found.

Server

  • JLT-142975 - Reduce CPU usage of real-time analysis for Business Transaction.
  • JLT-151504 - Don't accept licenses with unknown type
  • JLT-127317 - Server: Deadlock in connection handling
  • JLT-150781 - Improved completeness check for custom linked PurePaths in correlation-engine
  • JLT-150448 - The communication between collector and server can break (session closed with protocol dumps) caused by a race condition in the event buffer sender.
  • JLT-143551 - Security: Missing permission checks for plugin bundle management allowed non-privileged users to upload files.
  • JLT-143545 - Security Issue: Language pack deployment allowed to download more files than intended.
  • JLT-143612 - Security: System information feature was missing permission checks for file download.

UEM

  • JLT-151938 - Unspecified Error from checking xhr.status in aborted beacon signal in IE compat mode
  • JLT-151178 - UEM: JavaScript Agent: Dojo Sensor: Ajax request in the form of dojo.xhr.get( ) causes the web page to hang.
  • JLT-151819 - UEM: Undefined Error from a.originalXhr.readyState (is null or not an object)
  • JLT-151844 - UEM: High response time reported when an invalid URL causes jQuery $.ajax() to throw an exception.
  • JLT-144110 - Missing EndUser PurePaths when drilling down from a serverside Tier in EntryScreen.

PWH

  • JLT-140109 - Do not book dynamic WebRequest measure when config measure is skipped
  • JLT-151273 - Windows Performance Monitor measures may be scaled incorrectly on collectors running with Java 8


6.2.8 Resolved Issues

All resolved issues since 6.2.7

Server

  • JLT-136664 Fix memory problem during session reading when purepaths are linked with themselves.
  • JLT-150874 Importing a newer license with an unknown type breaks licensing UI.
  • JLT-150058 Fix a problem with 1.4 JVM memory-dump postprocessing
  • JLT-150064 Server: The 64-Bit variant of FlagUtils is not working correctly due to the use of a wrong datatype.
  • JLT-136160 Disk usage of sessions larger than reported by server. Added additional log output for better visibility and fixed a problem during visit-updates.
  • JLT-148400 In scenarios with 10+ real time worker threads, Dynatrace server is restarted due to watch dog timeouts caused by inefficient subscription processing.
  • JLT-130898 Next LogSpam: around MQMapping - reducing level to fine, which must be turned on, if there are any MQ mapping problems (Duplicate of JLT-140421)

Collector

  • JLT-148925 Malformed PurePath for HTTP requests when 6.1 agent connects to 6.2 collector
  • JLT-144364 Fix a problem that prevented agents to connect to collector during recovery.

UEM

  • JLT-150769 UEM: JavaScript Agent: Basic XHR sensor: Error "Invalid calling object" when calling the XMLHttpRequest open() method with an invalid argument.
  • JLT-146341 UEM: Java-based app server agent: invalid dtCookie content was logged as a Java IllegalArgumentException, is now a simple warning.
  • JLT-149329 UEM: JavaScript stack overflow error, when the bandwidth sensor is enabled.
  • JLT-150018 UEM: JavaScript agent can't detect it's features and no enabled modules are active due to non-working script-tag detection.
  • JLT-138989 UEM: Perceived Render Time can be larger than Page Load Response Time
  • JLT-143351 UEM: Perceived Render Time is incorrectly also sent if no window size could be calculated.
  • JLT-142532 UEM: Perceived Render Time slowest image url not available for source actions and deferred source actions.
  • JLT-137972 UEM: fix creating incidents based on concurrent visit measure

Java Agent

  • JLT-124563 Java instrumentation: Some classes can not be instrumended but hot sensor placement tried to change them and failed.

NGINX Agent

  • JLT-128200 Nginx: Removed dependency on Nginx's configuration changes. Removed 'No such file...' errors in logs.
  • JLT-134657 Nginx agent: All HTTP requests with missing headers are discarded and not processed.

Miscellaneous

  • JLT-148296 Drilldown from BT splittings in Dynamic Measure Matrix dashlet failed due to invalid filter settings.
  • JLT-147095 Improved error logging for Transaction Flow.
  • JLT-149658 REST Interface: can't retrieve specific host incident details
  • JLT-140421 MQ tag warning messages continuously appear in support logs. Reduce log level to fine, as this is usual to happen under certain circumstances.
  • JLT-135603 Log spam: Recieiving many maximum linked path depth of 500 reached errors: Reduce log interval but show affected PurePaths
  • JLT-148339 Incident information handed to user plugins may contain duplicated violation trigger values.
  • JLT-150631 Unix/Solaris: Zone specific memory usage is inaccurate/wrong because reading binary procFS 64bit process data from a 32bit process delivers invalid data.
  • JLT-150814 Fixed host health drilldown regression introduced with JLT-147478

6.2.7 Resolved Issues

All resolved issues since 6.2.6

UEM

  • JLT-142671 UEM: improve endVisit handling in order to let late incoming actions be assigned to a visit, which was already ended via endVisit event.
  • JLT-148129 UEM: Basic XHR sensor: When Content-Security-Policy is enabled, the use of (new Function("")) is flagged.
  • JLT-148365 UEM: Improve linking resources via CSS to action
  • JLT-148365 UEM: Improve linking resources via CSS to action
  • JLT-149327 UEM: Fix ConcurrentModificationException in VisitStoreAgingTimer which might happen after server restart due to visit recovery.
  • JLT-147187 UEM: JavaScript Agent: Basic XHR sensor: Error "Invalid calling object" or error "Cannot read property 'apply' of undefined" when calling methods on the XHR object
  • JLT-144282 UEM: Polling requests cause AngularJs actions to time out
  • JLT-145720 UEM: Fixed vulnerabilities in the handling of invalid requests in server-side agents.
  • JLT-144641 UEM: Correct version number handling for JS agent requests, in order to allow 2 digit revisions.
  • JLT-144416 UEM: ActiveXObject module causes responseText not being updated.
  • JLT-144105 UEM: Allow the '=' character to be included in HTTP header values that represent WebAPI tests.
  • JLT-140520 UEM: Activating Angular.JS causes page loading issues
  • JLT-142793 UEM: implement HttpServletRequest in order to let a proxied CacheHookingRequestWrapper have this interface as well.
  • JLT-142794 UEM: Overriding native removeEventListener function with deviant arguments can cause agent to execute these functions in an unexpected way.
  • JLT-145135 UEM: Active X Module causes out of memory exceptions when browsing hours on the same page on IE 7 and 8.
  • JLT-143827 UEM: AngularJS module causes TypeErrors in the document ready function
  • JLT-137130 UEM: Authentication sent via the XMLHttpRequest object is incorrectly handled or is blocked by the browser. Also, JavaScript events on the XHR.upload object are ignored.
  • JLT-144211 UEM: Adding multiple error listeners to jQuery ajax settings results in exceptions and non-executed callbacks.
  • JLT-143892 UEM: Mobile ADK receives incorrect monitor request name from agents. Webserver Agents Bug: Mobile ADK appends full monitor request path instead of the monitor signal name
  • JLT-140758 UEM: Fixing NullPointerException during "Stop UEM Debugging"
  • JLT-145033 UEM: Fixing StackOverflowException in UEM Correlation
  • JLT-144672 UEM: Loading actions last 180 seconds if dojo module is active.
  • JLT-143280 UEM: Time spikes in measures while using W3C Resource Timings
  • JLT-143130 UEM: Removing "If-Modified-Since" causes NPE on tomcat

Agent

  • JLT-148235 Browser Diagnostics: Update for native instrumentation data of Internet Explorer Rendering Sensor
  • JLT-148510 Global Agent time is not initialized properly on subAgent connect, and can be off for up to 10 seconds.
  • JLT-140137 Webserver Agent: fix crashes due to a zlib bug
  • JLT-148045 Added switch to disable dtCookieManager in the JavaScript Agent
  • JLT-145155 Java Agent: Missing jmx metrics due to NoSuchMethodError which occurred in some private fixpacks.
  • JLT-146585 WSAgent: Correct version number handling, support two-digit revisions in JS agent requests
  • JLT-142809 Webserver agent sends events for a transformation that was never registered
  • JLT-143007 Resolved duplicate class definition warning in combination with Wildfly and Java 8
  • JLT-141390 Apache agent: ETag headers that are removed from the response by mod_headers are restored again by the agent when UEM is enabled.
  • JLT-138621 Apache processes blocked by phpagent.
  • JLT-145002 Fixed potential IllegalAccessError with Java 8 and newinvokespecial.
  • JLT-141910 Apache agent: reduce the likelihood of a newly-spawned worker process handling the first few requests without an agent config due to SHM file spinlock contention (the most visible consequence being UEM functionality sporadically not kicking in).
  • JLT-144011 Browser Agent: Update for native instrumentation data of Internet Explorer Rendering Sensor
  • JLT-143908 Webserver Agent: Updated ignored filetype list for JavaScript Agent injection
  • JLT-143083 Webserver agents no longer cause skipped events/PurePaths after communication problems
  • JLT-144412 ArgumentException appears in PurePath when a WCF service uses OutgoingMessageProperties.
  • JLT-141252 Bad delegation suppression of WebService Sensor hurts (jdbc/exception) aggregation and sends empty nodes

Mainframe

  • JLT-145243 Correlation Engine: Circular linked purepaths caused by non-unique custom tags and a race condition.
  • JLT-148345 zRemoteAgent hangs at a handshake request from the zLocalAgent.
  • JLT-148113 zRemoteAgent crash during reconnect cycle.
  • JLT-144421 zLocalAgent deadlock can cause CICS disconnections to the zRemoteAgent
  • JLT-147876 possible zLocalAgent (zDC) cpu spin, while disconnected from the zRemoteAgent, only if ZIIP support disabled
  • JLT-145084 zLocal log files don't appear in the System Information dashlet
  • JLT-142582 Fix CICS Init issue during PLT, when the agent id doesn't flow quickly enough
  • JLT-125568 Reduced Agent GCP usage on z/OS
  • JLT-144959 Collector fail-over doesn't properly disconnect/reconnect the zDC and zLocalAgent.
  • JLT-138514 If the zRA is bounced with zIIP enabled, the zLocalAgent doesn't reconnect properly
  • JLT-142401 Socket connection errors with the zLocal and zRemote
  • JLT-141878 Crashes and connectivity issues with the zRemoteAgent

Server:

  • JLT-148864 Correlation blocked by synchronous communication to collector
  • JLT-148499 NullPointerException on agent deregistration after agent has been load balanced to a different collector
  • JLT-145459 Bug in processing of JMX measurements causes unnecessary commands being sent from server to agent.
  • JLT-147559 Exceptions during session-reading and not data available from PureLytics when using CICS agents that generate empty
  • JLT-148573 Server might cancel connection setup to collector where fixpack synchronization lasts longer than 2min
  • JLT-139487 Changed self-monitoring values for global Agent time. Improved logging in case of global Agent time problems.
  • JLT-145350 Communication: Fix race condition between collector/server time synchronization and collector/server agent registration. Some agents might not reflect the collector/server time difference correctly
  • JLT-137585 Improved robustness of server/collector sessions
  • JLT-145910 Fix race condition while serializing a request to the collector.
  • JLT-143998 Skipped purepaths and slow server performance.
  • JLT-145330 Fixes an issue where time calculation might be wrong for some Node.js PurePaths
  • JLT-141840 Fixed re-broadcasting of incidents from Backend Server to Frontend Server which could cause Out-of-Memory situations.
  • JLT-143661 Excluding class org.jboss.as.jmx.MBeanServerAuditLogRecordFormatter from instrumentation as it causes CPU overhead
  • JLT-141799 Introduce SessionSizeTracker for periodically checking and correcting real session sizes on disk.
  • JLT-143469 "Host Incidents" are not stored in continous recording session
  • JLT-142029 Enabling DTANG adapter may cause LDAP connections problems via SSL/TLS
  • JLT-145439 Failed Transaction drill-down opens ALL purepaths (no filter) for selected timeframe
  • JLT-136820 Reduce maximum age of ADMAnalyzer data in PureLytics by reducing the maximum timeframe and resolution in the ADMAnalyzer configuration.
  • JLT-143856 Host Monitoring: File system and nic exclusions do not apply for newly created system profiles
  • JLT-144166 PureLytics missing data due to UncategorizedRepositoryException (transaction aborted) after re-creating renamed system profile
  • JLT-142797 Outdated threshold values were used for triggering incidents from dynamic measures.

Collector

  • JLT-148362 NullPointerException in collector when opening UEM configuration.
  • JLT-143434 Collector connection problems ended up in a restart of the collector: prevent deadlock in static initializers
  • JLT-143193 Collector: Server considers Agent offline because it assumes that the Agent is connected to different Collector
  • JLT-142164 Fixed synchronization problem when using dynamically-sized buffers which lead to collector freeze/restart.
  • JLT-142731 Added collector flag that resolve IllegalAccessException in combination with java 8 and invokespecial
  • JLT-142531 Incidents: When confirming an incident based on a host performance measure, the measure becomes renamed and unusable.
  • JLT-146496 Fixing T3 instrumentation which hinders startup of managed Weblogic Application Server 12.2.1

Client

  • JLT-129816 Server Preferences Dialog: Server selection changes when selecting the License Overview
  • JLT-149132 Host dashlet generates invalid and incomplete XML reports.
  • JLT-147776 In pie charts the calculation of the total value was wrong in certain cases.
  • JLT-147406 Cannot create Monitor in Mac Client
  • JLT-135724 User Action PurePaths dashlet: include all columns when copy and pasting to Excel.
  • JLT-146131 User Action Health and Functional Health dashlet reports did not contain all data.
  • JLT-140769 Charting: When charting >= last 14 days with a 1d resolution, you'll get wrong values for the current day
  • JLT-144134 A specifically configured proxy may cause the client to use a plain connection instead of SSL/TLS.
  • JLT-141645 Client: Filter favorites are not preserved between invocations of the Client. The Client was trying to write to the installed program folder, rather than the user's home folder.
  • JLT-144469 Allow "count" aggregation for all measures in incident configuration.
  • JLT-143646 Not possible to create a trending memory consumption snapshot in the Mac OS X client.
  • JLT-146471 Percentiles: Wrong values when charting percentiles for purepath measures with more than one value per purepath

PHP

  • JLT-148726 PHP: PHP agent does not log into master agent until first packet arrives
  • JLT-139704 PHP: Add support for Postgres' PHP pg_pconnect() and Oracle ociexecute()
  • JLT-138873 PHP: Fixed issue: PHP FAST-CGI agent for Windows overconsumes licences

Mobile ADK (delivered in a separate artifact)

  • JLT-142541 Mobile ADK: iOS application has the potential to crash when calling [UIDevice setBatteryMonitoringEnabled:] either in the app or from 3rd party frameworks. This can happen because UIKit is not thread safe.
  • JLT-146281 Mobile ADK: iOS ADK calls wrong hooked method when super lifecycle method is called directly by an app outside of the lifecycle view call path.
  • JLT-141577 Mobile ADK: Hybrid Mobile instrumentation issues - iOS
  • JLT-145279 Mobile ADK crashes when addTarget is call while target is being disposed. There is a bug in iOS prior to 9.0 which causes viewDidLoad to get called if accessing the view during dealloc.

WebUI:

  • JLT-145223 [WebUI] Dashboards migration: "Internal server error" and MalformedInputException if system encoding changed (6.2+ has fixed UTF-8)
  • JLT-144396 Location for creating a web dashboard was pushed wrong to the browser from the rich client (fix for JLT-134795)
  • JLT-146275 Location for creating a web dashboard pushed to the browser from the rich client was not using the specified web server host.

Sensors:

  • JLT-146472 Fixing a possible NullPointerException for the Mule Tagging Sensor

Security:

  • JLT-143544 Security: Existing user could get access to other user password hashes and community credentials

6.2.6 Resolved Issues

Most important resolved issues since 6.2.5

Collector

  • JLT-137446 Collector/Server: StackOverflowError when sending CPU Sampling from Collector to Server and the InheritanceMap contains circular entries.
    • Impact: Collector crashes with StackOverflowError
    • Cause: Instrumented applications with massively changing class hierarchy across app-restarts (dynamic classes) cause loops in class cache
    • Solution: Prevent loops by detecting and using cached identical entries

All resolved issues since 6.2.5

Charting

  • JLT-140241 Last 30 minutes of a rate measure is not shown in chart.
  • JLT-141709 Last 30 minutes of a rate measure is not shown in chart. (duplicate of JLT-140241)
  • JLT-140547 Charting: When charting the splittings of a custom monitor plugin splitting dimension, the values and splittings were not entirely correct.
  • JLT-141288 Gap in charting Data due to timestamps not being updated on frontend server
  • JLT-140729 No data in chart for a specific resolution for all measures

Agents

  • JLT-141466 Apache agent does not update if isMasterAgentServiceInstalled is set to false.

Collector

  • JLT-142674 Collector: Connection problem with NumberFormatException in VersionAdapter class in server log if using plugins with a long value is used as build number
  • JLT-132788 Collector: ConcurrentModificationException when stopping the InheritanceMap while an Agent is unregistered.

Performance Warehouse

  • JLT-142226 Performance Warehouse: Under certain circumstances it can be that no measurements are written
  • JLT-142408 Performance Warehouse: Setting JDBCSocketTimeout does not work for Oracle because of incorrect value setting
  • JLT-141221 Performance Warehouse: No data written in even though connected if there was a problem with systemprofile synchronization.
  • JLT-141250 Performance Warehouse: Upon reconnect, analysis cache is started although it is disabled via server config.

UEM

  • JLT-135857 UEM: Unchecked characters in a cookie value cause a security vulnerability.
  • JLT-140567 UEM: Googlebot still visible after exclusion in configuration
  • JLT-141708 UEM: Bootstrapped JS Agent requests are returned with a 404 error.
  • JLT-141268 UEM: JS Agent can't be loaded when bootstrapper is used after upgrading.
  • JLT-142807 UEM: No visit created if changing from blocked application (e.g. via visit percentage) to non-blocked application
  • JLT-140662 UEM: Web requests with multiple redirects not linked to action

Client

  • JLT-128718 Client: Failed to save system profile due to revision mismatch

WebUI

  • JLT-141704 WebUI: Provide a way to differentiate between multiple monitors of the same type in the measure selection.
  • JLT-130188 WebUI: "Count" tile chart: Support and allow to select "Count" aggregation for measure charts
  • JLT-140411 Web UI: Duplicate colors in charts with more than 8 series.

Other

  • JLT-142424 Performance: Do not search for linked purepaths during session-read that have not been written to disk since they have been skipped.
  • JLT-141251 Some PurePaths were not shown until new PurePaths arrived.
  • JLT-137400 OneAgent: Enabled DtangAdapter would cause NullPointerException on collector when installing plugins.
  • JLT-138274 "A problem occurred while analyzing 'visits'" while reading Metrics from a session (e.g. Visit Dashlet)
  • JLT-141293 One parameter for the "Third Party content count" measure type was not saved.
  • JLT-141501 Server: Disk quota: Too much data removed due to DiskUsageHandler running twice
  • JLT-140951 PureLytics is missing one path read run if reading was stopped before end of session.

Mobile ADK (separate download):

  • JLT-128365 Mobile ADK: iOS auto instrumentation of apps containing A4SWebView may not work correctly.
  • JLT-141505 Mobile ADK: iOS: Web requests when using Alamofire are not timed and sent to Dynatrace server.

6.2.5 Resolved Issues

Most important resolved issues since 6.2.4

Collector

  • JLT-140086 Collector sends very small data packages to server, if compression is activated
    • Impact: Bad throughput on connections with high latency
    • Cause: Custom package header was written without using a buffer
    • Solution: Use a buffer for writing custom package header too

Agents

  • JLT-140382 NGINX Agent: Prevent instrumentation of unsupported PIE builds that could otherwise cause a crash
    • Impact: Attempt to use NGINX Agent with NGINX compiled as PIE would crash the whole NGINX process
    • Cause: PIE NGINX builds are not supported with 6.2, the Agent could not recognize indirection levels in offset data and attempted to reference memory outside process area
    • Solution: Both the script and the Agent recognize PIE NGINX builds, report errors and the Agent lets NGINX start uninstrumented
  • JLT-127616 PHP agent: SoapClient sensor: While creating dynaTrace tag, do direct manipulation on '_stream_context' object from Zend internals.
    • Impact: It may cause PHP / Apache to crash when SoapClient object was created without explicitly given 'stream_context'
    • Cause: PHP agent working with PHP Web Request sensor being on
    • Solution: PHP agent creates a 'steam_context' object to be able to tag outgoing requests

Mainframe

  • JLT-138259 No connection established with zRemote servers after CICS region recycle weekly. zRemote servers go down and don't come back up.
    • Impact: ZRemoteAgent crashed which caused a loss of connectivity from the CICS regions to the collector and server
    • Cause: The CICS recycle (actually the shutdown of it) caused the zRemoteAgent to enter a race condition.
    • Solution: Use a marked for deletion mechanism to indicate that the CICS region should be deleted

All resolved issues since 6.2.4

Agent

  • JLT-141049 Java Agent: NoClassDefFoundError for ImsTmResourceAdapterIntrospection due to missing version check
  • JLT-140406 Webserver Agent: Rework support for IIS 7.5.7601 metrics
  • JLT-138042 .NET Agent: Allow to disable crashdumps via debug flag
  • JLT-135327 Agent: Recurring "Instrumentation channel disconnected" for one agent after switching to next collector from group
  • JLT-139947 Classloader sync issue on Tomcat and Java 8
  • JLT-140413 Potential deadlock with Apache WebAppClassLoader and Java 8
  • JLT-140387 NGINX: Offset-generation script support for RHEL installations
  • JLT-137069 .NET Agent instrumentation appears to cause application to fail

Server

  • JLT-135118 Frontend Server: Charts are missing data due to invalid cache since upgrade to 6.2.2.1019
  • JLT-138549 Backend Server XXL Runs Low on Memory
  • JLT-132391 Server: Very long visits could result in SerializationException Only update latest session during periodic visit-update
  • JLT-138627 Frontend Server: NullPointerException in Repository.getIncidentRecordByRuleConfigReference()

Collector

  • JLT-140108 Collectors disconnected, ArrayIndexOutOfBoundsException collectors cannot reconnect until server restart
  • JLT-127948 Collector: Out of memory during memory dump due to huge (100's of MB's) strings.

Client

  • JLT-139863 Client: Mac: LDAP Group search filter truncated at the very last character
  • JLT-130611 Client: Incident Drill Down to PurePaths not working when condition is based on 'Count' or 'Sum' aggregation
  • JLT-133225 Client: Wrong legend for CPU usage (User and System inverted) in host information pane (infrastructure)

WebUI

  • JLT-138107 WebUI: gaps in web dashboard chart which disappear after refresh
  • JLT-134612 WebUI: Homescreen tiles use the wrong timeframe
  • JLT-130716 WebUI: VerificationException is thrown when "Add measure" is clicked for a chart-tile

UEM

  • JLT-138874 Added new debug flag for extended log when UEM path is skipped
  • JLT-139809 Javascript agent POST action reported to hang the webpage
  • JLT-136185 UEM: Firefox 3.5 and lower experience "Object.defineProperty is not a function" Javascript error

Mobile ADK

  • JLT-140528 Mobile ADK: Android: Javascript interface to support API 17+ and auto instrument web view for Cordova 4.0+
  • JLT-130445 Mobile ADK: Android: Some non-compliant Dalvik bytecode doesn't have InnerClass annotations, but we still need to preserve EnclosingMethod annotations
  • JLT-131207 Mobile ADK: Android: Add the ability for hybrid apps to set cookies for multiple domains.
  • JLT-134599 Mobile ADK: Android: Support for network connection other than WiFi and Mobile.
  • JLT-138818 Mobile ADK: iOS: INFO level logging is not working correctly

Mainframe

  • JLT-139531 zRemoteAgent crash after IPL of zDC's LPAR
  • JLT-138712 dtzAgent: IMS+CICS Agents broken if LMS Warnings while zIIP enabled

Other

  • JLT-124443 Skipped PurePath due to RTA queue maxed at 100k
  • JLT-140374 Class browser does not show data in conjunction with fix for JLT-134593
  • JLT-134593 Add md5 to hashcode of MetaClassKey to fix performance bottleneck in session-storage when lots of classes have the same name but different md5 (different loaded versions of a class)
  • JLT-140509 Exporting a session for certain purepaths fails
  • JLT-136117 PurePath for page load showing VisitID as '-' yet all subsequent related PurePaths contain the VisitID.
  • JLT-133311 Transaction Flow rendering could overload due to too many external services records
  • JLT-140380 The execute method of the action plugin is called incorrectly in 6.2
  • JLT-139706 Performance Warehouse: Low resolution duration reset to 1 day instead of 1 year (but server prevents purge thereafter)
  • JLT-135064 Environment Config Wizard auto-instrumentor path and monitor URL problems
  • JLT-134081 Failed to Save System Profile due to Revision Mismatch
  • JLT-129258 Session Storage Lost After License Change switching editions
  • JLT-119144 Do not reset ErrorDetectionRules when updates are rolled out
  • JLT-128314 .NET WCF over HTTP PurePaths do not contain Web Request URI Details and Response tagging for DCRum integration
  • JLT-138611 No Serializer found for Input com.dynatrace.diagnostics.global.customexternalcalls.CustomExternalCallConfig
  • JLT-129866 Browser performance report dashlet: Broken link to "Server side performance data" under 'Server' tab
  • JLT-138829 "Skipped Events (Server)" measure not working
  • JLT-138403 Error when sorting geographical locations by region
  • JLT-138645 Allow to import a CSV file for geographical locations that have an empty region field
  • JLT-127264 Dashboard source change causes a null pointer (text and measurement dashlet)
  • JLT-138472 Report generated for Database dashlet is not working correctly
  • JLT-138770 LogSpam around ApiPriorityMap
  • JLT-136755 "Smart Analytics engine skipped data" incident fired but not closed
  • JLT-137747 Can't send SSL email to port 25.
  • JLT-138288 SNMP Action Plugin - OID and type don't change for incident start/end
  • JLT-132385 Right click -> Create Measure and Right Click -> Create Business Transaction are non-functional from Remoting Dashlet

6.2.4 Resolved Issues

Most important resolved issues since 6.2.3

Server

  • JLT-137279 PurePath not analyzed because of time conversion problems (end time in the future)
    • Impact: The affected PurePaths will not be realtime analyzed, hence we have no measures / business transactions for them and are also not stored in the transaction store (Skipped non realtime analyzed PurePaths)
    • Cause: In rare situations the conversion from the timestamps that are delivered by the configured agent timer to an absolute time are wrong and can result in times that are in the future. Especially affected are agents running on Windows when the WPC (Windows Performance Counter) timer is used and the agent is started within ~15min after operating system startup. Other timers might be affected in very rare situation, the low-resolution timer is not affected.
    • Solution: Use an initial conversion factor in the correct resolution (milliseconds vs. timer dependent resolution)

Performance Warehouse

  • JLT-137391 Data loss for Oracle, DB2 and PostgreSQL performance warehouses after network outage between server and DB host
    • Impact: Data loss due to corrupt DB connection pool entry when using Oracle, DB2 and PostgreSQL DB hosts.
    • Cause: Incorrect recovery from network outage between server and DB host
    • Solution: Make DB-connection timeout independent from OS-connection timeout to properly discard of corrupt connection pool entries.

All resolved issues since 6.2.3

WebUI

  • JLT-135984 Freezing tiles due to JS Error in Safari 9+ due to wrong timing on svg element access.

Node.js (agent unchanged)

  • JLT-137416 PurePath nodes may be missing if they don't get an API assigned, i.e. mostly if they don't have an attachment
  • JLT-136326 Client: Add Tier Wizard: Corrected default collector port in require string.

Other

  • JLT-136933 Custom External Calls: Changes require server restart

6.2.3 Resolved Issues

Most important resolved issues since 6.2.2

Client

  • JLT-135581 After Mac OS X update, Dynatrace client might terminate when selecting measures
    • Impact: Dynatrace Client crashed after upgrading Mac OS X to El Capitan (10.11) and trying to add a measure to a chart.
    • Cause: When adding a measure the measure picker is opened and displays a spinner while the measure are loaded. This spinner crashed the client due to changed native Mac OS X APIs (system upgrade) and due to the legacy version of the SWT library we use.
    • Solution: The spinner widget within the measure picker was disabled for Mac OS X.
  • JLT-133229 Dynamic measure matrix (DMM) dashlet now works with new centrally stored host measures. 

    • Impact: Adding host measures to a dynamic measure matrix caused exceptions and/or dynamic host measures did not show up
    • Cause: a) DMM was not adapted to new central booking of host measures; b) data records shown in DMM were not compatible with new default sorting algorithms introduced with Java 7 which caused occasional exceptions.
    • Solution: a) Adapted DMM to also work with centrally booked host measures; b) removed inconsistencies from display data record to prevent sorting caused exceptions 
  • JLT-134743 Controlled rollout does not work for Java agents with a cell name 
    • Impact: An Agent selected in the Update Wizard is not updated if its name contains a square bracket (e.g., JavaAgent[App1])
    • Cause: The meta information that is contained in the cell part is not available at the time when the Collector decides which Core Agent version is provided to the Bootstrap Agent
    • Solution: The Update Wizard does not let you select an Agent with a square bracket in its name anymore, instead only the name without the cell part is listed.

Agent

  • JLT-132117 PHP terminates after assert and exception
    • Impact: Apache terminates due to core dump in PHP Agent
    • Cause: Incorrect return from zend_try in user function instrumentation, when instrumenting ‘Assert’, causes corrupted memory addresses in case of php error.
    • Solution: Wrapping zend_try blocks in native function, using C++ exception
  • JLT-132826 Instrumented Java application might not start up correctly if Sensor definitions on Collector are in a corrupted state
    • Impact: An instrumented Java application might terminate during startup with a “java.lang.NoSuchFieldError: dt_initialized” error message
    • Cause: If for some reason the Sensor definitions at the Collector are corrupted and missing vital instrumentation information, the resulting instrumentation can be corrupted
    • Solution: Every time an Agent connects to the Collector, the Collector will check for the correctness and consistency of the Sensor definitions or otherwise don’t instrument the Agent 
  • JLT-131082 ThreadTagging sensor and static constructor of the Agent class can cause a deadlock. 
    • Impact: .NET application deadlocks at startup.
    • Cause: Race between 2 threads where thread A is processing the static agent initializer, which instantiates an object that tries to acquire a lock and  thread B, also using that object, holds the lock but waits for the static agent initializer to complete.
    • Solution: Object instantiation is now done lazy outside the static agent initializer.
  • JLT-134876 MessageBroker Agent: Performance degradation in instrumented code when Agent not connected to Collector
    • Impact: User applications observed outages due to a performance degradation when Message Broker Agent lost its connection to the Collector.
    • Cause: Due to network issues the MB Agent was not able to connect to the Collector, but still tried to instrument and send data over blocking calls, thus causing a serious performance impact on the user’s application.
    • Solution: As soon as the MB Agent detects connection loss it switches into “disabled” state and does no longer try to instrument and send any data. When the connection to the Collector can be re-established, it resumes normal operations.
  • JLT-132551 CICS Agents don’t re-register with the Server when the zRemoteAgent machine is restarted
    • Impact: No CICS/IMS agents can register with the Dynatrace server
    • Cause: When the zRemoteAgent machine was rebooted, the disconnected TCP/IP connection was not handled correctly by the zLocal Agent on z/OS
    • Solution: The new libdtzagent.so for z/OS (the zLocalAgent) detects this situation properly

Server

  • JLT-135121 Deadlock in Backend Server when DiskUsage Handler tries to delete recently switched session which is currently updated
    • Impact: Dynatrace Server restarted by native launcher due to deadlock.
    • Cause: Occurs when: The diskusage handler (1) tries to delete a session which was switched recently (2) when this sessions needs to be updated (3).
    • Solution: Prevent deadlock by limiting the wait time for the lock. The update is lost, but the session gets deleted anyway.
  • JLT-135760 Slow merging of cached transaction flow entries can cause Frontend Server to go out of memory
    • Impact: OutOfMemoryError on frontend server
    • Cause: Merging of a large number of transaction flow entries can block processing of cache data.
    • Solution: Usage of lookup maps speeds up merging significantly
  • JLT-135534 Time conversion from Agent time to Server time can be far off when using hardware timer
    • Impact: PurePaths are skipped from real-time analysis and session storage because their start time/end time is very old. Elapsed time column within a PurePath delivers inaccurate values.
    • Cause: The hardware timer uses a wrong frequency for its time conversions when running on Intel CPUs which support Turbo Boost on Linux. 
    • Solution: Hardware timer calibrates itself during agent startup to deliver the correct frequency
  • JLT-128469 Removing timing correction for PHP requests on server 
    • Impact: Incorrect execution time displayed for pure path nodes
    • Cause: Server corrects tick count of events sent from PHP agent, which is unnecessary since PHP buffers events on Agent side
    • Solution: Server now detects events from PHP agent and does not correct timings

UEM

  • JLT-126385 UEM: Basic XHR Detection hides XMLHttpRequest.prototype properties, causing "'property' in XMLHttpRequest.prototype" checks to fail. 
    • Impact: JavaScript if-statements fail for ‘property’ in XMLHttpRequest.prototype, where they should normally succeed.
    • Cause: To capture all necessary information, the XMLHttpRequest object must be wrapped. Wrapping of it’s prototype object wasn’t part of the process, thus some properties were missing.
    • Solution: All original prototype properties are synchronized to the wrapped XMLHttpRequest object, thus none should be missing and mentioned checks should succeed as expected.
  • JLT-130098 UEM JS Agent: Plugin "l", addeventlistenerwrapper: Error "Object doesn't support this action"
    • Impact: JavaScript error "Object doesn't support this action" occurs with the UEM JavaScript Agent's advanced addEventListener feature (plugin "l") on web pages that contain certain ActiveX-based <OBJECT> elements, when displayed in Internet Explorer, when the page unloads. One example of this is in Microsoft's CRM product.
    • Cause: Some ActiveX-based objects don't behave well when the JavaScript Agent attempts to clean-up object external references during the page unload.
    • Solution: We now ignore this benign error

WebUI

  • JLT-132104 WebUI: Worldmap on home screen is empty at first 
    • Impact: World Map tile doesn’t display map after receiving bad or null UEM data
    • Cause: If an error occurred due to bad or null UEM data, the map wouldn’t be drawn. If good data was received afterwards, there was no reattempt to draw the map without refreshing the page in the browser.
    • Solution: Map drawing errors are now tracked and used to trigger another attempt at drawing the map upon receiving updated UEM data.

Mobile ADK (separate download)

  • JLT-133166 Mobile ADK: Using Address Sanitizer in Xcode 7 with the iOS mobile agent causes a crash
    • Impact: Mobile application will crash on start up.
    • Cause: sscanf is used against a character array that is not properly terminated and causes a heap-buffer-overflow error. 
    • Solution: The character array is now properly terminated preventing the heap-buffer-overflow error.
  • JLT-129063 Mobile ADK: iOS mobile application does not function as expected when using ASIHTTPRequest
    • Impact: Mobile application will not function as expected when making a http request using ASIHTTPRequest.
    • Cause: Dynatrace mobile agent replacement delegate was not responding to all selectors required by ASIHTTPRequest
    • Solution: Dynatrace mobile agent now correctly forwards unknown selectors to the original delegate.

All resolved issues since 6.2.2

Server

  • JLT-132811 Server: Watchdog restart due to InfrastructureConfigCenter blocks multiple threads because its listeners are called within synchronized blocks
  • JLT-132530 Server: Incident message like "ERROR-FORMAT-STRING" for out-of-memory incidents when description provided by VM is empty
  • JLT-133748 Server: AnalysisCache: Possibly lost visits due to missing flush of VisitAnalyzerMap
  • JLT-127362 Server: Renaming previously renamed system profiles to original name causes DataIntegrityException in Analysis Cache
  • JLT-133830 Self-Monitoring: Dynatrace server performance impact because of too many splittings due to Collector groups.
  • JLT-133098 Server: Log spam "obviously invalid hopcount" when endless loops are instrumented
  • JLT-126069 Server: Potential log spam in InfrastructureConfigCenter in case of missing host

Collector

  • JLT-137255 CollectorCenter: Wrong collector peer returned if agentinfo.collectorinfo is null

Agents

  • JLT-134659 Agent: Access Denied exception on Windows during multiple bootstrap agent start ups causing due to broken inter process mutex (requires new agent installer)
  • JLT-135197 Agent: Under rare circumstances the autosensor overhead on Unix systems might be higher than expected
  • JLT-130751 Agents: Make web request query subject to global string length limit
  • JLT-129860 Agent: AIX CPU utilization calculation shall consider correct entitlement and CPU time stealing/donation.
  • JLT-134015 Agent: Host metric "Page Faults" on AIX: Use more representative value "PgspIn" (see vmstat)
  • JLT-135988 Agent: RDTSC timer seems to report the wrong time (in ms)
  • JLT-130215 PHP Agent: Log Spam "Blocked path arrived".
  • JLT-132606 Nginx Agent: Improved offsets application.
  • JLT-132585 Webserver Agent: Added metrics support for IIS 7.0.6002.
  • JLT-134026 Webserver Agent: Added metrics support for IIS 7.5.7601.

Client

  • JLT-134202 Client: Application Environment Configuration Dialog empty when opened via start center when server of the selected system profile differs from currently active dashboard.
  • JLT-131874 Client: Show info in Start Center and Agent Overview for outdated bootstrap agents with a major version smaller 6
  • JLT-135855 Client: Make traffic light charts work with host measures again.
  • JLT-133007 Client: .NET Thread Dump Beta Warning shows up for CPU sampling and Memory Analysis too
  • JLT-134685 Client: Enabled DOTALL mode for regex evaluation in rich client filter bars in order to evaluate multiline values correctly.
  • JLT-135482 Client: Lost connection to Server and could not reconnect again due to socket closed exception: Improve debug logging

WebUI

  • JLT-135421 WebUI: Omni channel dashboard without data due to ConcurrentModificationException in DynamicMeasureRefresher
  • JLT-131905 WebUI: Updated highcharts to current version.
  • JLT-134795 Location for creating a web dashboard was pushed wrong to the browser from the rich client
  • JLT-132633 NullPointerException: Uncaught Webui REST exception: WebuiExceptionMapper toResponse

UEM

  • JLT-136318 Visits in self-monitoring profile are count down from UEM volume falsely.
  • JLT-125494 UEM: Correct calculation of license volume consumption for long running visits and extended visit timeout of 1h
  • JLT-128033 UEM: NumberFormatExceptions in correlation if frameactions whose parents contain special characters are sent.
  • JLT-136008 UEM: Basic XHR Module throws exception when used in some older browsers.
  • JLT-130471 UEM: Enabled use of browser's navigator.sendBeacon() to send the JS Agent's dynaTraceMonitor signal.
  • JLT-135203 UEM: dynaTraceMonitor terminated with whitespace characters causes java.lang.NumberFormatException during parsing and leads to dropped user action 
  • JLT-128472 UEM: JavaScript Agent throws exception: "a.split is not a function" for clicked anchor tags whose href-attribute is set to "javascript:...", which are children of SVG tags.
  • JLT-135669 UEM: Add sanity check for high latency values sent from JS agent.
  • JLT-126148 UEM: Enabled use of browser's navigator.sendBeacon() to send the JS Agent's dynaTraceMonitor signal.
  • JLT-132142 UEM: "Capture Events" causes up to 10 second delay in event firing
  • JLT-122606 JS agent not injected by web server because compressed content is treated as uncompressed.
  • JLT-135227 UEM: Some keypress events cannot be captured if browsers are too slow.
  • JLT-134198 UEM: lastModification for JS bootstrapper must be in milliseconds instead of microseconds

Mainframe:

  • JLT-135321 Memory leak in zRemoteAgent when fetching zLocal log files
  • JLT-132815 Memory leak in zRemoteAgent when fetching zLocal log files
  • JLT-131694 IMS TM Resource Adapter sensor: PurePaths not stitched together due to NullPointerException

Other

  • JLT-135242 Host marked "-" appears in Performance Monitor due to inconsistencies in monitor/host linking after certain host data updates
  • JLT-125363 Infinite loop in MQ mapping utility due to inconsistent mapping configuration.
  • JLT-133662 Generic Execution Plugin not showing in Infrastructure Incident Action Menu

6.2.2 Resolved Issues

Most important resolved issues since 6.2.1

Server

  • JLT-130816: Performance Warehouse: No data stored due to disconnect, but shows as connected

    • Impact: In special network scenarios (dead network connections), no data is written to performance warehouse although its status is still shown as connected
    • Cause: Default JDBC socket timeout might be to high
    • Solution: JDBC socket timeout can now be changed via server option com.dynatrace.diagnostics.repository.jdbcsockettimeout
  • JLT-131383: Performance Warehouse on MS SQL Server: Data integrity violation: Duplicate key row in object dbo.dynamic_measure with unique index uk_dynamic_measure
    • Impact: Occurs only with Performance Warehouse on MS SQL Server and enabled automatic detection of applications. The error happens if multiple applications are detected which have the same name but different use of capital and small letters
    • Cause: Dynatrace uses a case insensitive database on MS SQL Server.
    • Solution: Additional server option, com.dynatrace.diagnostics.analyzers.realtimeapplicationautodetectionpreanalyzer.tolowercase, allows conversion of detected applications to lowercase
  • JLT-122968: Dynatrace Server restarts due to StackOverflowException in Correlation Engine
    • Impact: Dynatrace Server restarted by native launcher due to StackOverflowException
    • Cause: Non-unique custom tags caused the Correlation Engine to run into an infinite recursion, causing the dynaTrace Server to crash with a StackOverflowException
    • Solution: Internal correlation mechanism now detects inconsistent tag data and terminates PurePath correlation deterministically.
  • JLT-132046: Count values for Business Transactions diverge over time between Charts and Business Transaction Dashlets
    • Impact: Affects only measurements which are booked with a timestamp that is more than one minute in the past
    • Cause: Measurements can be booked up to ten minutes in the past. The charting cache within Frontend process (introduced in 6.2.0) ignored updates for aggregations older than one minute
    • Solution: Improved caching mechanism
  • JLT-126464: Rate measures do not show any values
    • Impact: All custom rate measures (Metric group: "Calculation") are affected
    • Cause: Synchronization issue between Frontend and Backend process
    • Solution: Rate measure are now correctly synchronized Frontend and Backend process

Collector

  • JLT-130260: Under certain circumstances the installation of an update on a Dynatrace Collector requires an additional manual restart
    • Impact: Automatic Collector restart prevented after update installation
    • Cause: When an update installation fails (e.g. due to a I/O error while writing to disk or wrong permissions), a NullPointerException prevents an automatic restart of the collector
    • Solution: Error handling triggers an automatic restart and clean-up of the Dynatrace Collector
  • JLT-133458: High Collector memory usage due to incorrect cache sizing
    • Impact: Collector uses too much memory, which might cause Agents to be declined
    • Cause: Wrong debug flag constant was used for cache sizing
    • Solution: Using correct debug flag now
  • JLT-133626: Duplicate Collector entries after upgrade from 6.2.0 to 6.2.1 (inconsistent FQDN/host name detection)
    • Impact: Collectors show up multiple times, with only the host name changed. Monitors may not execute anymore as their schedule's target may not match.
    • Cause: Hostname detection may be inconsistent since 6.2, due to DNS
    • Solution: Pre-6.2 behavior can be enforced by setting com.dynatrace.diagnostics.enforceSimpleHostname=true

WebUI

  • JLT-130504: Web Dashboard Chart tiles may lead to a JavaScript exception
    • Impact: Empty Dashboard charts and/or JavaScriptException: "(TypeError) : undefined is not an object (evaluating 'a.e')"
    • Cause: Implementation expected a resizing timer to exist, which was not always the case
    • Solution: Null-reference check added for resizing timer

MessageBroker

  • JLT-123178: MessageBroker Agent memory leak
    • Impact: Memory usage of MessageBroker Agent steadily increases over a few days for certain workflows
    • Cause: Under certain circumstances the Message Broker Agent is not notified about transaction termination. Internal PurePath information for such workflows was kept until Agent (MessageBroker) restart
    • Solution: The MessageBroker Agent checks on transaction start for non-terminated (outdated) PurePaths and frees related resources

PHP

  • JLT-131347: PHP worker processes terminate unexpectedly
    • Impact: With PHP autosensors turned on, PHP child processes may terminate and restart
    • Cause: Under a certain race condition, PHP autosensors may be reading invalid webserver configuration
    • Solution: PHP agent now applies reference counting for webserver configuration

UEM

  • JLT-127596: jQuery sensor may cause TypeError / "Object expected"
    • Impact: Potential JavaScript TypeError / "Object expected" error in jQuery 1.9.1 (and above) during unload phase
    • Cause: jQuery sensor sets data object to null in unload phase
    • Solution: jQuery sensor now restores originally wrapped object
  • JLT-131017: Visits: Client data is shown as "unknown"
    • Impact: Visit dashboard shows client data (e.g. browser, operating system) as "unknown"
    • Cause: Caused by reading/writing updated browsers.xml with different encodings on server and client
    • Solution: browsers.xml now being written with consistent encoding. Customers might need to remove update.properties from users home, e.g. C:\Users\<username>\.dynaTrace\dynaTrace 6.2\client\conf in order to force re-updating local files

MobileADK

  • JLT-130236: Mobile ADK: Android: Compatibility with Webserver Agent
    • Impact: When migrating from Dynatrace 6.0 to Dynatrace 6.1 or 6.2, 6.0 Android Mobile Agents (version lower than 6.0.0.7132) will no longer capture UEM data
    • Cause: Due to a protocol change between Dynatrace 6.0 and 6.1, 6.0 Android Mobile Agents (version lower than 6.0.0.7132) get a response from 6.1/6.2 Java or Webserver Agent that they can’t handle
    • Solution: Introduced debug flags debugUemMobileStatus60Java for the Java Agent and debugUemMobileStatus60Native for the Webserver Agent, which then send responses in the 6.0 protocol format. IMPORTANT: Current 6.1/6.2 Android Mobile Agents do not understand the 6.0 protocol format, so when setting this debug flag please ensure to use the newest Android Mobile Agents

All resolved issues since 6.2.1

Server

  • JLT-130202: Frontend server runs out of memory and restarts
  • JLT-130852: Measure threshold update frequency is too low on Frontend server
  • JLT-130619: Dashboards do not provide data after migration to 6.2
  • JLT-122968: Dynatrace server might restart due to StackOverflowException in Correlation Engine
  • JLT-130920: Hostmeasures are not recorded in session unless they are exported
  • JLT-126747: Two incidents using same measure with condition aggregation "min" fire simultaneously
  • JLT-126090: Available agent metric shows invalid value in case of collector loss when using collector groups
  • JLT-130816: Performance Warehouse: No data stored due to disconnect, but shows as connected
  • JLT-131383: MSSQLServer: Data integrity violation: Duplicate key row in object dbo.dynamic_measure with unique index uk_dynamic_measure
  • JLT-132750: Self-Monitoring Collector fails to start causing a Server restart loop
  • JLT-132046: Count values for Business Transactions can diverge over time between Charts and Business Transaction Dashlets
  • JLT-129349: [Licensing] Grace volume isn't considered when checking remaining volume for uem-reservation
  • JLT-122631: Frontend Server: AssertionError while storing a session / entry screen refresh during manual session recording
  • JLT-128800: Visit store statistics do not contain clientTypeName "Desktop"

Collector

  • JLT-133626: Duplicated collector entries after upgrade from 6.2.0 to 6.2.1 (inconsistent FQDN/host name detection)
  • JLT-130260: Under certain circumstances the installation of an update on a Dynatrace Collector requires an additional manual restart
  • JLT-133458: High Collector memory usage due to incorrect cache sizing 

Agents

  • JLT-129768: ASP.NET Counters are not collecting data
  • JLT-131822: No data from agents on 6.0 or 6.1 collectors with 6.2 servers and injection failed
  • JLT-121213: WebSphere MessageBroker: Method argument value on routeToLabel is corrupt - the argument was not registered properly for nodes of type ComIbmRouteToLabelNode
  • JLT-129552: CICS/IMS subagent: Elapsed time (duration) computed incorrectly due to bad tickcounts from tick delay
  • JLT-122260: Initial startup time is not correct for Mainframe Subagents
  • JLT-128126: zRemoteAgent crash on zDC reconnect with many CICS regions
  • JLT-129250: zRemoteAgent and zLocal Not Reconnecting After Collector Restart
  • JLT-128280: zSystems integrated information processor service request block is not posted when the zLocal closes the socket
  • JLT-130367: zLocal socket to zRemoteAgent is being forced to non-blocking - needs to be blocking
  • JLT-128521: Optimized zLocal Idle thread to save mainframe CPU time
  • JLT-131834: Java Agent: Threading Sensor: removed log spam: "[threading ] saveTraceTagInfoToFieldThreadStartExit EXIT LINK AREA"
  • JLT-116242: java.lang.NoClassDefFoundError: com.dynatrace.diagnostics.agent.Agent
  • JLT-128779: Dynatrace Browser Agent shows 0.0 seconds render time with IE11
  • JLT-122094: Passing a non-string URL value to XHR.open() causes JavaScript error "a.indexOf is not a function"
  • JLT-125883: Several improvements on Dynatrace javascript regarding dtcookie handling
  • JLT-129839: Java agent on linux x64 causing the JVM not to start
  • JLT-125583: NGINX: Agent doesn't work after kernel upgrade due to prelink usage
  • JLT-111594: Node.js Agent: Link web requests to UEM visits
  • JLT-132251: Provide Option to derive CICS Subagent name from Agent Properties
  • JLT-132311: 6.0 mobile ADK compatibility: Webserver agent adaptions
  • JLT-130742: Java Agent: ClassFormatError: "Duplicate method in name&signature" on SUD startup with Java 8
  • JLT-130621: ZIIP Thread not re-enabled when zIIP and TxB are on, and zRA is restarted
  • JLT-130760: Include Nginx agent logs in support archive
  • JLT-128892: Java Agent: Logging Sensor: Decrease Overhead at log level TRACE caused by reflection calls
  • JLT-129783: Broken purepaths occur when running Soap CICS Start transactions

MessageBroker

  • JLT-123174: WebSphere MessageBroker: Memory leak - In certain situations PurePaths were not released when an exception occurred on fetching the PurePath
  • JLT-123178: WebSphere MessageBroker: MessageBroker Agent memory leak
  • JLT-123657: WebSphere MessageBroker: Memory leak due to a race condition during purepath cleanup
  • JLT-127589: Websphere MessageBroker: Invalid Purepaths in Client and Agent log

Client

  • JLT-130778: No left Y-Axis legend in dual chart
  • JLT-129358: Collector Hosts are shown offline in Infrastructure view
  • JLT-131975: Monitoring Dashboard Host Health: Dialog: NullPointerException in HostRequestResponseHandler
  • JLT-126802: Test Automation dashlet: No data shown because RecordQueue is full
  • JLT-125099: Full analysis of user actions dashlet loses tree format
  • JLT-127978: "An error occurred while creating the dashlet content" appears when using "Show in Dashboard" feature of the system monitoring dashboard.
  • JLT-130124: Removed overlapping state-borders in the USA (worldmap).

UEM

  • JLT-126858: AngularJs sensor wrappers do not always initialize early enough and thus do not create actions
  • JLT-126919: UEM Visit Tagging not working for most visits
  • JLT-127596: jQuery sensor may cause TypeError / "Object expected"
  • JLT-131017: Visits: Client data is shown as "unknown"

WebUI

  • JLT-133025: Business transaction list: Include in OOTB dashboards
  • JLT-132007: Business transaction list: Configuration breaks if not closed correctly. 
  • JLT-131921: Business transaction list: Show warning for adding a result measure only if user clicks on done-button
  • JLT-133019: Legend toggle control is missing in tile preview
  • JLT-131384: Tile triggers 2 chart requests after switching to tile preview
  • JLT-130504: WebUI Chart tiles may lead to a JavaScript exception
  • JLT-130503: Uncaught client-side WebUI exception occurred: JavaScriptException: (TypeError) : b[e] is undefined
  • JLT-129047: Feature update: BT List tile, iframe tile, Dashboard overview splitted, Process-Host linking
  • JLT-130127: Done button gone for Pie Chart Measure Edit on Chrome with 1280x800

Sensors

  • JLT-127239: Disable [ESB] Enhanced WSO2 tagging via Debug flag
  • JLT-128163: Support HTTP tagging for Axis 1 clients (both regular and alternative package names from PEGA)

Charting

  • JLT-126464: Rate measures do not show any values
  • JLT-104088: Server: Add debugging information for baselining

MobileADK

  • JLT-133166: iOS: Application crashes when building with Xcode 7 and turning on the Address Sanitizer. 
  • JLT-132030: iOS: Device log contains error message in iOS9
  • JLT-127593: iOS: UIControl events not firing
  • JLT-126224: iOS: EventHandler of instrumented app executes twice instead of once
  • JLT-130380: Android: Crash with the Android ADK - WebView is missing (due to Android L)
  • JLT-130236: Android: Compatibility with Webserver Agent

Other

  • JLT-131035: Transaction flow time spent in External Service not subtracted from calling tier for API 'Web server'
  • JLT-129114: Implicit usage of LocalXAConnectionFactory from org.apache.commons.dbcp.managed.BasicManagedDataSource causes invalid database schema names
  • JLT-128608: REST API should return error when attempting to register test run with disconnected PWH

  • JLT-129347: node.js Update

 

6.2.1 Resolved Issues

Server

  • JLT-129764 Frontend Server: Self-monitoring collector is constantly reconnecting to collector since upgrade to 6.2.1
  • JLT-129357 Server should not trigger the deletion of a Collector FixPack not matching its minor version
  • JLT-127853 Watchdog restarts frontend server when PWH is not available
  • JLT-128903 Server: Aggregate message queue nodes in ADMAnalyzer by setting "com.dynatrace.diagnostics.adm.analyzer.aggregateMessagingNodes" to true
  • JLT-127629 Server: PathDataRequirement for SessionReading during Analysis Cache runs reads too much data
  • JLT-127923 Backend server: NullPointerException in VisitStore.recoverVisitsFromContinuousSessionRecording prevents startup
  • JLT-128793 Frontend server: Analysis cache: Handle exceptions in ProviderReadThread by skipping session.
  • JLT-126952 Renaming measures or agent groups while system profile is changed by someone else results in a system profile serialization error and reboot of backend server to resolve
  • JLT-128557 Sensor packs partially deleted from Server directory by Selfmon Collector on UNIX based systems

Collector

  • JLT-129248 Collector: Wrong detection of Fully Qualified Domain Name
  • JLT-129376 Collector: NullPointerException in InstrumentationCacheManager when pre-6.2 agents are connecting
  • JLT-128002 Collector: Report instrumentation error to the agent also on cached instrumentation results.
  • JLT-123792 Fully functional collector is shown with "orange" status
  • JLT-116245 Fix race condition in agent connection handling where agent would remain in a half-connected state until collector is restarted.

Performance Warehouse

  • JLT-128435 Performance Warehouse: Add more information for repository connection state change logging
  • JLT-128756 Performance Warehouse: Migration loses historical data

Agents

  • JLT-129621 Agent: Logs output to system-out/err due to DT_DISABLEINITIALLOGGING not working
  • JLT-127914 PHP Agent: opcode manipulation must be disabled with zend guard / loader
  • JLT-126876 PHP Agent: Version 5.5 on Windows: Not starting, compile with VisualC++ 11
  • JLT-125318 Java Agent: Java 8: Fixed IllegalAccessError when using a private static method as a reference
  • JLT-103420 Java Agent: Don't handle request in UEM sensor if excluded on servlet sensor
  • JLT-125476 Added enhanced debugging for performance counters plus performance counters which can not be found will now be skipped instead of terminating the complete counter retrieval process.
  • JLT-123152 Agent bootstrapping race condition leads to agent start-up problem.
  • JLT-128447 Self-monitoring agents consume a java license if these agent cannot be instrumented during startup

Client

  • JLT-130732 Client: Cannot edit system profile on a 6.2.X server if client is running 6.2.Y
  • JLT-130182 Client: Missing entry points in entry screen
  • JLT-127981 Client: ConcurrentModificationException in ServerSettings > Infrastructure when deleting label with 2+ hosts
  • JLT-128893 Client: Accessing resources fails with NoSuchElementException
  • JLT-127971 PureStack Manually created hosts are not considered in filtering

UEM

  • JLT-130136 UEM: Fix evaluation of visit user experience, if long running action is evaluated after subsequent action.

WebUI

  • JLT-128103 WebUI: Dashboard stored when leaving details view in view mode
  • JLT-128708 WebUI: Gap in data occurs when timeframe last 1 hour is selected.
  • JLT-127951 Baselining charts only show dots when timeframe is set to 30min

Other

  • JLT-127836 Missing/incomplete PurePaths and "Rule ID could not be resolved for method rule" in collector log
  • JLT-124436 Mobile ADK: Calling endVisit can cause lifecycle actions and web requests to get sent twice to the server
  • JLT-110325 Combined fixes to update to latest available version.

 

 

  • No labels