Skip to end of metadata
Go to start of metadata

September 26th 2016

Become a performance hero with built-in tuning expertise

This latest AppMon release empowers your teams to ensure high quality earlier in the development cycle and to communicate more effectively when problems are detected during production. Having analyzed thousands of user sessions over the years, our performance experts have identified a number of common, easy-to-resolve performance pitfalls that may be affecting the performance of your applications. AppMon now automatically shows you which components and processes can be optimized, thereby freeing up your performance experts to focus on the really tough issues.

        Get AppMon 6.5 for SaaS

 
 What's new in Dynatrace Application Monitoring and UEM 6.5?
 

End-to-end insights. All the time.

When application status turns red, you need to find out where, why, and how big the impact is. With Dynatrace AppMon 6.5, you provide constructive input rather than ask questions.

  • Become your team's best friend. With AppMon insights, whether you're talking to operators about an unhealthy host, to developers about PurePaths that unnecessarily spam the database, or your managers about user experience following a move to the public cloud, you'll be able to provide constructive input that's meaningful and to the point.
  • Slice-and-dice your monitoring results. Transaction flow show you which components take the most load and contribute the most to your app's response time. When status turns red, you're one click away from knowing if your real users have been impacted and whether or not you need to seek the assistance of your developers or operators. And the best part? Transaction flow is now fully customizable.

Pro-active application tuning

Dynatrace AppMon analyzes every single PurePath to automatically detect common pitfalls that our performance experts have identified over the years. Such built-in insights give your teams immediate feedback regarding quality degradations during the development phase. This frees up your performance experts to focus on the really tough issues.

Learn more!

  • Real-time feedback regarding quality degradations. Has a recent code change resulted in a bad search query spamming your database? Because AppMon captures and analyzes every PurePath, it automatically discovers anti-patterns (for example, N+1 problems) during testing–thereby helping you avoid problems later in production when traffic levels are much higher. 
  • Move to production with confidence. 80% of the insights that our experts have gleaned through manual analysis of problems over the years are now embedded into AppMon's analysis engine and are available to your teams. This means you won't have to bring in your performance experts late in production to deal with big problems that could have been addressed earlier during testing when the problems were smaller and more manageable.

Empower your frontend developers

When your business stakeholders worry about the reasons behind bad user experience, or your support team turns to your frontend developers for solutions to user-experience problems, AppMon UEM provides the perfect solution for finding the answers you need.

  • Quickly identify the root causes of bad user experience! Top findings for each visit reveal if problems originate on the frontend, the backend, or with third party content.
  • Understand how users navigate through your application! Analyze the full click path of each user visit in the new AppMon web UI.
  • The newly redesigned JavaScript agent architecture has even less impact on the performance of your web applications and it's easier to use in scenarios where  auto-injection isn't an option.

More heads are better than one

You can now compare data within custom time frames when working with Dynatrace AppMon 6.5 web dashboards and tiles. Custom time frames, custom colors, and new report sharing options help you level up your reporting game.

  • Custom time frames for tiles & dashboards: Compare technical and business-relevant data using either relative or custom time frames for dashboards and tiles.
  • Custom colors for measures and splittings: Create executive-ready dashboards by highlighting important facts with custom colors.
  • Improved access controls: You can define access for single or multiple users, or make your dashboards available to a broader audience without login.
  • +1 for all teams: Once you favorite a dashboard, its popularity increases. So your teams immediately see which dashboards provide the most valuable insights.

 

Non-HTTP applications, annual usage-based licensing, and self-service licensing

  • Gain an overview of non-HTTP-based applications and services.

  • Save money with annual usage-based licensing. Ideal for sites that have variable traffic levels.

  • Manage your licenses with self-service licensing (beta).
  • Use flexible agent units with online licensing (beta) to minimize administration.

 

100% cross-platform visibility

Monitor all your applications regardless of where they're hosted. From mainframe, to microservices in the cloud, deploying AppMon has never been easier. The following support is now available with AppMon 6.5:

Full steam ahead

Dynatrace AppMon 6.5 makes communication between your teams more effective. Web dashboards make the sharing and reporting of data easy. And now, with the introduction of top findings for PurePaths and UEM visits, your support and development teams can provide detailed, actionable data to your performance experts when problems are detected.

We scale with your business

Ready to scale up with Dynatrace? We're happy to announce that our recent architectural advances are now bearing fruit:

  • This release introduces support for 5x more system profiles (from 20 up to 100), providing you with the configuration flexibility you need to scale your business and application environment with robust stability and performance.
  • With this release, we've leveled up the maximum number of transactions/sec on a single server that AppMon can support. We've pushed the limit to +30% transactions/sec.
  • 3x faster performance for PostqreSQL clean-up through database partitioning.

Stay tuned for even more architectural and scalability enhancements in the next release! See the new Deployment Guide for detailed hardware recommendations specific to your load.

Confident continuous innovation

Improve your delivery cycles, catch bad code early in the development lifecycle, and reduce the amount of time spent firefighting issues in production.

  • Automate Web performance optimization across all browsers (mobile and desktop). Track key architectural metrics (e.g., number of images, JavaScript files, external resources, and database calls) captured by the UEM JavaScript agent in UI-driven/browser tests using your favorite framework, such as Selenium or Appium.
  • Speed up development: Testing and debugging in your preferred IDE has never been easier. You can instrument your application and tests without leaving Eclipse, IntelliJ IDEA, or Visual Studio and jump directly from any PurePath to the corresponding code to fix issues.
  • Continuous Integration Integration: the Gradle Plugin now available in addition to the already existing Ant/Maven/NAnt & MSBuild Plugins for integration in CI Builds
  • Test automation samples library: Browse through our open source Test automation samples library and integrate metrics-driven continuous delivery into your test process. Samples are available for Selenium, Saucelabs, JMeter, SoapUI, Maven, Ant, REST API test automation, and more.

Extended database insights, now also available for MySQL

Identify and solve the database issues that impact application performance! Now, in addition to support for Oracle and SQL Server, our Database agent also supports MySQL.

  • MySQL: Identify database issues out-of-the-box with the Database Health dashboard. Review execution plans to figure out why a specific SQL statement is slow.
  • SQL Server: Advanced visibility into stored procedures, support for Windows authentication / Active Directory users.
  • Improved RAC support: Oracle RAC instances show you how each cluster instance behaves. Cluster nodes are automatically discovered during agent setup.

OkHttp, Retrofit, jQuery, WildFly, and much more...

This release introduces support for a number of technologies. For full details see System requirements.

    • Azul JVMs: Zulu and Zing are now supported on Linux 64bit

    • .NET: ASP.NET Core 1 on full framework (beta)

    • Node.js: Support for v6. Introducing code-level visibility and memory-/CPU metrics

    • Host-Agent: Process availability monitoring for any process on the host
    • Mobile: OkHttp 3 & Retrofit 2 are supported for Android auto instrumentation

    • UEM: jQuery 3

    • Application Server: WildFly 9 & 10,  IBM WebSphere Liberty 8.5.5.6 to 16.0.0.1

Be a part of our active APM community!

For deeper insights, install plugins for the technologies you use:

  • Redis monitoring plugin: Get more insights into your in-memory-database!

  • Visual Studio 2015 extension: Launch your application from Visual Studio 2015 with injected AppMon agents. Jump directly to the source code from PurePath.
  • Real-time data feed listener: Get live metrics from AppMon and include them in, for example, your automatic test run reports.
  • UEM heatmap: Create click heat maps to visually understand what your users are doing (see example on the left).
  • Generic measure monitoring plugin: Allow external test tools such as JMeter and LoadRunner to feed measures into AppMon.
  • Demandware fastpack: Provides deep insights into your demandware eCommerce platform.
  • New version of Jenkins plugin: Offers new features and UI.

Community enhancements:

  • Access and search the AppMon open Q&A forums without logging in.
  • Easier navigate through our community with the new navigation bar

 

 Upgrading and getting started with this release

No matter your role or use case, the Get Started guide has you covered:

 Licensing update

Fewer editions. Simplified licensing.

Beginning with AppMon version 6.2, we reduced the number of available commercial editions. Production Edition and Pre-production Edition are all you need now. The Test Center edition has been renamed "Pre-production" and the Development Team Edition has been deprecated.

Dynatrace 
Edition

6.1 and earlier

6.2

6.3 and later
Development Team Edition(tick)(warning) 1(error) 2

Pre-Production Edition
(formerly Test Center Edition)

(tick)(tick)(tick)
Production Edition(tick)(tick)(tick)

1 ) Development Team Edition license for 6 or 6.1 still works 
2 ) Development Team Edition will not be supported going forward (contact your sales representative for conversion options)

General Information

Due to the extensive list of new features and improvements in AppMon 6.5, it's necessary that you obtain a new license to migrate from a previous version. You can upgrade an existing license on your own using our eServices license management portal. For full details, see the license upgrade documentation. If you require support or have questions, our licensing management team will gladly help you with upgrading your current license to a version 6.5 license.

Following a license upgrade, ensure that your current license is deactivated. If you're using UEM, ensure that the correct amount of UEM volume is reissued in the form of UEM vouchers.

AppMon for z/OS still uses a MIPS-based licensing model but Compuware's License Management System (LMS) has been deprecated. Beginning with the 6.3 release, z/OS licenses are now only available through eServices. IMS and CICS regions (sub agents) need to be listed as z/OS agents. Java and native agents running on z/OS are now also licensed through the Dynatrace AppMon server.

 Resolved and known issues

Resolved issues

This release contains a huge number of quality improvements. Most of them were also pack-ported to 6.3 and delivered through updates.

 Resolved issues in 6.5.0

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.

Known issues

While new product releases are tested extensively with all supported platforms and technologies, certain issues can't be addressed by the product. Please refer to our Knowledge Base for other workarounds and tips.

 

 System requirements & supported technologies

Unable to render {include} The included page could not be found.

 Support levels and End of Life policy

Introducing a new support policy

A new and predictable End of Life policy was introduced with version 6.2 to better facilitate planning for updates and migrations.
End of Life dates are now announced together with release dates. New versions are fully supported for at least 18 months and support for critical production issues is provided for an additional 6 months (premium support required). This policy applies to Dynatrace AppMon & UEM 6.2+. Previous versions remain on the former policy!

Support level and End of Life overview 6.2 and higher

Product
version

Release
date 

Support
status

Full support
until

Limited support*
until 

2018 October (7.2)October 8, 2018(tick)April 30, 2020October 31, 2020
2018 April (7.1)April 3, 2018(tick)October 31, 2019April 30, 2020
2017 May (7)May 31, 2017(error)November 30th, 2018

Jun 1st, 2019

6.5September 26, 2016(error)June 30, 2018September 30, 2018
6.3February 29, 2016(error)August 31, 2017February 28, 2018
6.2June 29, 2015(error)December 31, 2016June 30, 2017

*) Premium support required (severe production problems of monitored applications only)

Support level and End of Life overview 6.1 and lower

Product  
version

Release
date 

On-demand
support

End of Life

6.1December 9, 2014(error)February 28, 2017
6July 17, 2014(error)October 31, 2015
5.6January 15, 2014(error)June 1, 2017
5.5 and earlier (error) 

Platform support changes

  The Dynatrace AppMon 6.5 release discontinues support for the following platforms and components:

  • Dynatrace Bootstrap agents < version 6
    The bootstrap agent was designed to allow easy upgrades of Dynatrace agent code by simply applying an update to the Dynatrace server and restarting the targeted Dynatrace agent’s application process that the agent is injected into. Before version 6.x the bootstrap agent was mainly untouched. However due to customer suggestions to further enhance the bootstrap agent functionality, improvements were added to the 6 & 6.3 base (bootstrap) agent to enhance the ability of upgrading agents injected into applications with the Controlled Rollout feature.

  • Dynatrace browser agents for Firefox and Internet Explorer
    Due to technical restrictions imposed by browser vendors, we have to discontinue the use of native browser agents. In response we extended our JavaScript-based agent (part of UEM) with diagnostics capabilities (details see "Confident continuous innovation" in the 6.5 release notes).

  • Dynatrace Client 32bit (upgrades from earlier releases & 32bit webstart client supported)
  • Dynatrace Server 32bit (memory restrictions)
  • Dynatrace Client on Mac OS X 10.7 (EoL by Apple Sep 29,2014)
  • For all Dynatrace components: LZO (Lempel–Ziv–Oberhumer) compression
  • Hadoop and HBase sensors, features, and dashboards are removed (e.g., Hadoop jobs overview)
  • .NET 2.0 (EoL by Microsoft Apr 12, 2016)
  • .NET 3.0 (EoL by Microsoft Jul 12, 2011)
  • HP-UX IA64 (no hardware available by HP)
  • Java Virtual Machine 1.4.2 (all vendors, EoL by Oracle Oct 30, 2008)
  • Java Virtual Machine 5 (all vendors, EoL by Oracle May 31, 2015)

  • Internet Explorer 7 (EoL by Microsoft Jan 12, 2016)
  • Limited support for IE9, 10 (e.g., Impact resource timings will be removed, only basic metrics are available)
  • Microsoft SQL Server 2005 (EoL by Microsoft Apr 12, 2016)
  • JBoss 5.x (EoL by Red Hat Nov, 2016)
  • PHP 5.2 (EoL by PHP Dec 16,2010)
  • Cosminexus 8 (EoS of JVM 5)
  • Software AG WebMethods 8.2 (EoS by Software AG Jun 30m 2015) 

With the next Dynatrace AppMon release (planned for May 2017), support for the following platforms will be discontinued:

  • No labels
Page: Dynatrace AppMon 6.5.38 Release Notes Page: Dynatrace AppMon 6.5.37 Release Notes Page: Dynatrace AppMon 6.5.36 Release Notes Page: Dynatrace AppMon 6.5.35 Release Notes Page: Dynatrace AppMon 6.5.34 Release Notes Page: Dynatrace AppMon 6.5.33 Release Notes Page: Dynatrace AppMon 6.5.32 Release Notes Page: Dynatrace AppMon 6.5.31 Release Notes Page: Dynatrace AppMon 6.5.30 Release Notes Page: Dynatrace AppMon 6.5.29 Release Notes Page: Dynatrace AppMon 6.5.28 Release Notes Page: Dynatrace AppMon 6.5.27 Release Notes Page: Dynatrace AppMon 6.5.26 Release Notes Page: Dynatrace AppMon 6.5.25 Release Notes Page: Dynatrace AppMon 6.5.24 Release Notes Page: Dynatrace AppMon 6.5.23 Release Notes Page: Dynatrace AppMon 6.5.22 Release Notes Page: Dynatrace AppMon 6.5.21 Release Notes Page: Dynatrace AppMon 6.5.20 Release Notes Page: Dynatrace AppMon 6.5.19 Release Notes Page: Dynatrace AppMon 6.5.18 Release Notes Page: Dynatrace AppMon 6.5.17 Release Notes Page: Dynatrace AppMon 6.5.16 Release Notes Page: Dynatrace AppMon 6.5.15 Release Notes Page: Dynatrace AppMon 6.5.14 Release Notes Page: Dynatrace AppMon 6.5.13 Release Notes Page: Dynatrace AppMon 6.5.12 Release Notes Page: Dynatrace AppMon 6.5.11 Release Notes Page: Dynatrace AppMon 6.5.10 Release Notes Page: Dynatrace AppMon 6.5.9 Release Notes Page: Dynatrace AppMon 6.5.8 Release Notes Page: Dynatrace AppMon 6.5.7 Release Notes Page: Dynatrace AppMon 6.5.6 Release Notes Page: Dynatrace AppMon 6.5.5 Release Notes Page: Dynatrace AppMon 6.5.4 Release Notes Page: Dynatrace AppMon 6.5.3 Release Notes Page: Dynatrace AppMon 6.5.2 Release Notes Page: Dynatrace AppMon 6.5.1 Release Notes Page: Dynatrace AppMon 6.5 Mainframe Release Notes