Skip to end of metadata
Go to start of metadata

2017-04-10

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

Resolved and Known issues

6.3.23.1012 Resolved Issues

57 (+ 3) critical issues, 696 (+ 17) total resolved issues

 Component change overview
ComponentTotalNew
Client931
Collector461
Communication80
DotNETAgent91
HostAgent50
InstallerAndBuild30
JSAgent10
JavaAgent393
MainframeAgent331
Mobile350
NGINXAgent70
OneAgent10
PHPAgent20
PWH240
Plugins30
Server1903
ServerCorrelation160
ServerRTA151
UEM1122
WebUI232
WebserverAgent312

Most critical issues since the last public updates

UEM

  • JLT-174021 - User Action BT filtering doesn't seem to work (requires server flag "com.dynatrace.diagnostics.enableTargetAttachmentForEndUserAnalyzer")
    • Impact: Although the filtering works it can happen that splittings contain "filtered" values.
    • Cause: Analyzer for User Action BT splitting uses different target page values than analyzer for filtering.
    • Solution: Use the same target page values for splitting and filtering.

MainframeAgent

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

WebserverAgent

  • JLT-185144 - Introduce debug flag "debugiissuppresspecialrequestresponseflushnative" to avoid flushing the special request response immediately as this allegedly causes memory corruption.
    • Impact: Due to corrupted memory the w3wp crashes.
    • Cause: A call to IHttpResonse::Flush seems to cause memory corruption in certain situations.
    • Solution: Introduce debug flat "debugiissuppresspecialrequestresponseflushnative" to disable flushing and check if this solves the problem.

All resolved issues

Client

  • JLT-184787 - NullPointerException when checking for required restart during collector configuration

ServerRTA

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

DotNETAgent

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

JavaAgent

  • JLT-146567 - PMI measure aquisition not working for some WebSphere rare configurations.
  • JLT-184856 - java.lang.NoSuchFieldError: dt_CursorId when using MongoDB Java Driver 3.4.x
  • JLT-177618 - Detect Java 9 and disable Agent.

UEM

  • JLT-174021 - User Action BT filtering doesn't seem to work.
  • JLT-182152 - Fixed division by 0 during 3rd party measurement evaluation.

Server

  • JLT-158972 - Error during session timeframe calculation due to synchronization issue in session registry.
  • JLT-176183 - Problems post-processing memory-dumps on analysis-server as the available diskspace is out of sync
  • JLT-184809 - NullPointerException in CollectorCenter

WebUI

  • JLT-185123 - Drill down into South Sudan is impossible on the World map.
  • JLT-184623 - For some countries the drill down from World map to User analytics does not show any data.

Collector

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

MainframeAgent

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

WebserverAgent

  • JLT-184789 - Introducing troubleshooting debug flags debugIISExperimental1 thru 6 for analyzing IIS agent related problems.
  • JLT-185144 - Introduce debug flag "debugiissuppresspecialrequestresponseflushnative" to avoid flushing the special request response immediately as this allegedly causes memory corruption.

6.3.22.1016 Resolved Issues

54 (+ 1) critical issues, 679 (+ 23) total resolved issues

 Component change overview
ComponentTotalNew
Client923
Collector451
Communication80
DotNETAgent81
HostAgent50
InstallerAndBuild30
JSAgent10
JavaAgent361
MainframeAgent320
Mobile351
NGINXAgent70
OneAgent10
PHPAgent20
PWH240
Plugins30
Server1879
ServerCorrelation160
ServerRTA144
UEM1103
WebUI210
WebserverAgent290

Most critical issues since the last public updates

DotNETAgent

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

All resolved issues

UEM

  • JLT-182291 - Performing a filter in the Visits Dashlet, that included a regular expression with escape characters, failed to return the correct results.
  • JLT-181576 - Wrapped two mobile correlation log messages around the com.dynatrace.diagnostics.debugMobileCorrelation debug flag to prevent log spam.
  • JLT-178799 - Prevent mobile application detection for mobile apps called 'Default Application'

Server

  • JLT-184188 - Fix a deadlock during session-storage management on backend server.
  • JLT-152245 - Visit recovery could fail under very specific circumstances due to a synchronization issue.
  • JLT-163215 - Occasional NullPointerException when trying to read already closed session file
  • JLT-182994 - Self-monitoring Collector binds wrong agent listen port if '-listen' argument is passed to dtserver process)
  • JLT-178859 - License UEM reservations for autodetected applications were falsely possible.
  • JLT-180558 - Occasional IllegalArgumentException when sorting tree of AgentOverview portlet for reporting because comparison method violates its general contract
  • JLT-170558 - Occasional IndexOutOfBoundsException in BaselineChartingMeasurementAggregator
  • JLT-181554 - Open incidents duplicated for rules not marked "Store in Performance Warehouse" when saving system profile.
  • JLT-183006 - Mobile Workload Dashlet Displays Insufficient Permissions for User with Administrative Rights

ServerRTA

  • JLT-184860 - Reversion of JLT-184273 and JLT-182766 due to Null Pointer Exceptions
  • JLT-184273 - On server startup visit store aging timer will be started after finishing measure subscription.
  • JLT-182766 - Optimization introduced with JLT-142975 turned on by default
  • JLT-163216 - In realtime analysis check and log entry added to avoid NullPointerException

Client

  • JLT-183173 - Client crashes when a dashboard containing a dual axis chart with a timeframe offset gets too small.
  • JLT-182907 - Open in client link not working when using non standard port for client to server connections
  • JLT-183732 - Failed transaction percentage measure not correctly drilling down to filtered purepath, instead shows all

Collector

  • JLT-173181 - Current server session is closed on collector because collector watchdog is not notified while waiting for send buffer.

JavaAgent

  • JLT-182957 - Logging sensor with empty severity doesn't work as exepcted

DotNETAgent

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

Mobile

  • JLT-182921 - Android Agent: increase max length to 255 for action names and web request urls

6.3.21.1008 Resolved Issues

53 (+ 1) critical issues, 656 (+ 14) total resolved issues

 Component change overview
ComponentTotalNew
Client891
Collector440
Communication80
DotNETAgent70
HostAgent50
InstallerAndBuild30
JSAgent10
JavaAgent350
MainframeAgent321
Mobile343
NGINXAgent70
OneAgent10
PHPAgent20
PWH243
Plugins30
Server1784
ServerCorrelation160
ServerRTA100
UEM1071
WebUI210
WebserverAgent291

Most critical issues since the last public updates

UEM

  • JLT-180550 - High number of incomplete visits and high AppMon server memory usage
    • Impact: High number of incomplete visits observed after updating to 6.3.18, 6.3.19 or 6.3.20
    • Cause: New map implementation within VisitStore: Special condition can lead to broken visit aging, i.e. visits never get completed.
    • Solution: Corrected handling of empty maps in VisitStore

All resolved issues

Server

  • JLT-180355 - Wildcard '*' is not applied in ignore mount point rule in infrastructure
  • JLT-164742 - Self-monitoring Collector might not be able to connect to AppMon Server if custom Collector connection settings are used
  • JLT-173387 - DssService does not always delete temporary files
  • JLT-171070 - Prevent the creation of system profile names with trailing space characters or special characters via REST interface

PWH

  • JLT-180774 - Introduce debug flag to restrict performance warehouse incident retention time.
  • JLT-178723 - Frontend server sometimes does not reconnect to performance warehouse after backend server restart.
  • JLT-181526 - Cleanup task may delete open incidents from performance warehouse.

UEM

  • JLT-180550 - High number of incomplete visits and high AppMon server memory usage

WebserverAgent

  • JLT-180810 - Time provider logging never showed up in master agent logs

MainframeAgent

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

Mobile

  • JLT-181446 - Android Auto-Instrumentation: Missing lifecycle instrumentation if activity class hierarchy was distributed over multiple dex files
  • JLT-180108 - iOS Agent: Improved compatibility with LP-Messaging
  • JLT-180814 - iOS Agent: Improved handling of local URLs

Client

  • JLT-179170 - Sanity check in EntryScreen

6.3.20.1009 Resolved Issues

52 (+ 1) critical issues, 642 (+ 12) total resolved issues

 Component change overview
ComponentTotalNew
Client882
Collector443
Communication80
DotNETAgent70
HostAgent50
InstallerAndBuild30
JSAgent10
JavaAgent350
MainframeAgent310
Mobile310
NGINXAgent70
OneAgent10
PHPAgent20
PWH210
Plugins30
Server1741
ServerCorrelation161
ServerRTA100
UEM1065
WebUI210
WebserverAgent280

Most critical issues since the last public updates

Client

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

All resolved issues

Client

  • JLT-169266 - Saving DB Agent configs shouldn't throw NullPointerException.
  • JLT-162000 - Improved logging for case when collector is not found when configuring DB Agent.

ServerCorrelation

  • JLT-148746 - Application name is not set on timed-out pure-paths because application name is set on exit event which is not received in case of time-out.

UEM

  • JLT-174352 - Added missing documentation and provided links for 'Map detected Domains to Third Party and CDN' and 'Advanced Configuration for Captured Resources' dialogs
  • JLT-178943 - NullPointerException in WorldMap when server is connected
  • JLT-179196 - fixed NPE in application drop-down in UEM settings
  • JLT-179153 - fixed AIOOB exception when parsing beacon
  • JLT-178752 - If an XHR happens during beforeunload, pagehide or unload, source actions cannot be linked to subsequent load actions.

Collector

  • JLT-179029 - Broken reconnect of 6.1 agent when connecting to 6.3 collector and later
  • JLT-178279 - T3 stitching not working with Weblogic 12.2.1.2.0
  • JLT-178885 - Improve logging if Agent connection can't be established due to synchronization problem.

Server

  • JLT-178530 - Incidents originating from measures of Frontend Server may not trigger properly.

6.3.19.1011 Resolved Issues

51 (+ 2) critical issues, 630 (+ 11) total resolved issues

 Component change overview
ComponentTotalNew
Client862
Collector411
Communication80
DotNETAgent71
HostAgent50
InstallerAndBuild30
JSAgent10
JavaAgent350
MainframeAgent310
Mobile310
NGINXAgent70
OneAgent10
PHPAgent20
PWH210
Plugins30
Server1734
ServerCorrelation151
ServerRTA100
UEM1012
WebUI210
WebserverAgent280

Most critical issues since the last public updates

UEM

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

Server

  • JLT-177072 - Host health incidents are always sent, even at configured downtimes
    • Impact: Incident downtimes have no effect on host health incidents, they are always fired
    • Cause: Host health incidents are fired for the Infrastructure system profile, but there is no incident rule engine to disable for this profile
    • Solution: An incident rule engine is also created for the Infrastructure system profile so that incident rules can be disabled for this system profile. Note that host health incidents can only be suppressed globally via incident downtimes of the Infrastructure system profile or global downtimes, downtimes on other system profiles will have no effect.

All resolved issues

DotNETAgent

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

Server

  • JLT-178317 - dtcmd (separate download): listing agents fails in case eventcount, skippedevents, skippedpurepaths or totalPurePathCount counters have values above 2^31-1.
  • JLT-176157 - Fix server stops recording (manual) with full storage queue, nothing written to manual recording session.
  • JLT-172415 - Logfile pollution caused by NullPointerException in UemSignalMessageProcessor
  • JLT-177072 - Host health incidents are always sent, even at configured downtimes

UEM

  • JLT-177131 - AngularJs de-support success and error callback methods
  • JLT-176370 - After creating a Web Request Response Time measure and restarting the server, the measure was missing from the measures list.

Collector

  • JLT-172311 - User Plugin logging may be impacted by malformed log messages.

ServerCorrelation

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

Client

  • JLT-177201 - Update Wizard: "Would lose fixes" message causes IllegalArgumentException when a language pack is installed
  • JLT-168322 - DB Agent: Getting explain plan for queries with whitespaces leads to message "The db did not return any explain plan for the query. It is possibly no longer cached"

6.3.18.1010 Resolved Issues

49 (+ 0) critical issues, 619 (+ 17) total resolved issues

 Component change overview
ComponentTotalNew
Client844
Collector402
Communication80
DotNETAgent60
HostAgent50
InstallerAndBuild30
JSAgent10
JavaAgent350
MainframeAgent310
Mobile310
NGINXAgent70
OneAgent10
PHPAgent20
PWH210
Plugins30
Server1695
ServerCorrelation140
ServerRTA100
UEM992
WebUI211
WebserverAgent283

Most critical issues since the last public updates

All resolved issues

Collector

  • JLT-170763 - Fixed a very rare connection interruption between collector and server.
  • JLT-171391 - Incorrect data for some files in tablespaces report from Live View for Oracle DB Agent.

Server

  • JLT-170005 - Load balancing task failed to calculate average load for masterAgents properly in certain cases.
  • JLT-172297 - Fix a potential problem that led to exceeding the max entry-size of sessions files while updating visits in session-storage.
  • JLT-172449 - Business Transaction stopped reporting data without reason
  • JLT-171613 - Frontend Process: Running Low on Memory: Improve realtime mapping parsing performance
  • JLT-154333 - Collector grouping causes load balancing task to behave weired, if only one Agent connected (Agent was forced to bounce around the Collectors).

Client

  • JLT-175834 - Older servers may cause an error in Start Center: There was an error checking the servers certificate and key pair: chain is null/empty or keystore error.
  • JLT-175965 - NPE in System Information Dashlet
  • JLT-173073 - Agent group settings of inactive system profile configuration may be pasted
  • JLT-170704 - Client connections tunneled sometimes caused configuration issues when using multiple servers.

UEM

  • JLT-166037 - ActiveX XHR plugin does not capture requests on IE11.
  • JLT-164893 - Fix IllegalPathModificationException in UEM correlation: deactivate handling for creating a root action based on a user action info in a root error.

WebserverAgent

  • JLT-165484 - IIS Agent causes a content length mismatch when the two newlines after the response header section are split into two fragments
  • JLT-171042 - Use default agent configuration whenever a sub agent detects a shared memory version mismatch to turn that sub agent off.
  • JLT-171041 - Update shared memory file version manually to avoid unnecessary incompatibility issues between master and sub agents.

WebUI

  • JLT-166444 - Added alternative country name support to the world map.

6.3.17.1019 Resolved Issues

Most critical issues since the last public updates

MainframeAgent

  • JLT-174301 - zRemoteAgent crash while handling subagent license verification.
    • Impact: The zRemoteAgent will crash, and need to be restarted.
    • Cause: The message handlers were not fully initialized when the license verification was received.
    • Solution: Verify that the handlers are initialized, and if not, wait for the next 5 minute DTAX cycle.

ServerRTA

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

All resolved issues

Server

  • JLT-171686 - Copying and pasting a system profile that was created from a system profile template creates another template, not an actual system profile
  • JLT-165160 - Added license exhaustion information to dtactivation
  • JLT-172778 - Change RTA subscription to use fast subscription mechanism by default, see debug flag "com.dynatrace.diagnostics.rta.fastsubscription"
  • JLT-166130 - Self-monitoring task sometimes stops working without further notice

InstallerAndBuild

  • JLT-172837 - License text file was outdated

Client

  • JLT-173005 - Certificate warning was not shown properly when Chinese or Japanese language pack was installed

Collector

  • JLT-173433 - RMI sensor causes VerifyError with Weblogic 12.2.1.2

UEM

  • JLT-172672 - Perceived render time URL may contain full image-data and thus invalidates beacons.
  • JLT-172055 - XMLHttpRequest actions time out if beforeunload event is aborted by a user.
  • JLT-174389 - Non-http protocol href values trigger fake beforeunload causing action timeouts
  • JLT-175163 - If a page leave is aborted, some JavaScript agent values aren't reset, which might lead to 180 second timeouts.'
  • JLT-171687 - reduce time-tolerance for linking web requests to actions in order to avoid wrong linked web requests due to long running actions.
  • JLT-173327 - Bandwidth calculation was always downloading all 6 image files irrespective of connection speed.

WebUI

  • JLT-147989 - Scrolling on home dashboard is not possible on mobile devices.

PWH

  • JLT-173053 - Very long incident properties cause a PWH exception (Data integrity violation)

MainframeAgent

  • JLT-173194 - Fix Version....... build date/time stamp for the zLocalAgent
  • JLT-174301 - zRemoteAgent crash while handling subagent license verification.

ServerRTA

  • JLT-169819 - Agent group selection on business transaction measure configs changes on it's own without user intervention

WebserverAgent

  • JLT-171696 - Nginx agent crash when handling large POST uploads.

6.3.16.1014 Resolved Issues

Most important issues since the last public updates

UEM

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

Server

  • JLT-170420 - MQ Mapping with custom tagged PurePaths: Unlinked PurePaths
    • Impact: Some MQ mappings (custom tags based on MQ data), which rely on a proper setup of the server side MQ mapping structure, failed causing unlinked MQ custom tagged pure paths.
    • Cause: With startup optimizations reading mqmappings.xml (Client and Server) a regression was introduced in building up the internal server side MQ mapping structure only partially.
    • Solution: The full server side MQ mapping structure preparation is now again performed with server startup, while it is still omitted in the client side (where MQ mappings are not needed anyway).

ServerCorrelation

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

All resolved issues

Client

  • JLT-128883 - Controlled Fixpack Rollout: Update Wizard shows incorrect number of selected (to be updated) agents
  • JLT-165877 - Fixed a scrolling issue for Network and Disk charts in the Host Details View.

Mobile

  • JLT-141079 - Android agent: improve background detection for Android 5.0+ devices
  • JLT-171203 - Android agent: increased Java heap size for auto-instrumentation (for Windows)
  • JLT-171317 - Android agent: improved communication handling when agent can't connect to dynatrace monitor server.
  • JLT-171450 - Android Agent: patch aapt to provide missing application-label output to avoid client crash in instrumentation wizard

JavaAgent

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

UEM

  • JLT-155524 - reset BT calculation values before starting analysis for a new visit, otherwise BT results get corrupted.
  • JLT-159316 - JSAgent XHR plugin: Upload fails with "TypeError" error when polyfill is present on Array.
  • JLT-168444 - If a link redirects to a different subdomain, Dynatrace doesn't capture the click on the link even if both pages are instrumented.
  • JLT-169198 - Only book measures from server-side PurePath on visit, if PurePath is not linked to an action. Booking is therefore delayed and done by VisitStoreAgingTimer as soon as we definitely know, that a server-side Path is not linked.
  • JLT-170447 - Evaluate event time before adding to UEM queue and add queue limit in order to prevent endlessly growing UEM queue.
  • JLT-171277 - Added the new name of Czechia as an alternative name for the Czech Republic.
  • JLT-171605 - AngularJS module breaks the page when expecting the version object

Server

  • JLT-161351 - Integrity check fails on system profile clone after creating agent group from template
  • JLT-169112 - Fix race condition when processing CPU sampling events while the CPU sampling task is closed.
  • JLT-170253 - Fix potentially incorrect counts in error-detection dashlet.
  • JLT-170420 - MQ Mapping with custom tagged PurePaths: Unlinked PurePaths
  • JLT-170648 - EntryPoint analyzer incorrectly distinguishes the same method from different agents or sessions.
  • JLT-170700 - Improve session reading performance when lots of threads are involved on purepaths.
  • JLT-170767 - External HTTP call is not shown in WebRequest dashlet
  • JLT-170843 - Fix potentially non-matching counts in ErrorDetection and ErrorDetection Details.
  • JLT-170960 - Improve session reading performance for visits.
  • JLT-171448 - Fix a potential race-condition between continuous integration component and session storage that can lead to lost CI data
  • JLT-171670 - Update GeoIP Databases and User Agents to prevent outdated mappings or unknown User Agents
  • JLT-171898 - Fix an issue where the server would spam OneAgents with identification requests when they would connect via a collector

Collector

  • JLT-166464 - JDBC connections opened during testing of DB Agent configuration are not closed properly.

PWH

  • JLT-170248 - Malformed SQL in DB2 performance warehouse, fixed with alternative statement.

WebserverAgent

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

ServerCorrelation

  • JLT-171788 - Server crash due to stack overflow during completeness check of very deep PurePaths.

6.3.15.1050 Resolved Issues

Most important issues since the last public updates

Client

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

UEM

  • JLT-168828 - Documents which are exported via PureLytics Stream will be dropped if the contain '.' in field names
    • Impact: Missing User Actions and Visits.
    • Cause: BT names will be added as field in the exported document. BT names can contain '.', which are prohibited in fields by Elasticsearch
    • Solution: Replace '.' with '_' in field names.

All resolved issues

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.
  • JLT-143311 - Agent group filtering not working correctly for charts
  • JLT-168426 - Server certificate evaluation in the client received more data than necessary.
  • JLT-169686 - A minimum dashlet size of 100x100px would always be enforced.
  • JLT-170284 - The context toolbar border is not shown when hiding the dashlet header

ServerRTA

  • JLT-150888 - Execution/CPU times per API differ between Layer Breakdown, API Breakdown and PurePath view

ServerCorrelation

  • JLT-161609 - Very deep linking of root execution paths may lead to stack overflow during completeness check and consequently to server crash.

JavaAgent

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

WebserverAgent

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

Server

  • JLT-165090 - Improve session-reading performance for visits in case lots of visit-sessions must be read.
  • JLT-165110 - Unable to apply host filters to monitor measures due to different host name and host address
  • JLT-169136 - Security/Keystore refactoring to reduce code complexity
  • JLT-169613 - Cannot find a matching SUD for the agent in AvailabilityCenter on agent state update
  • JLT-170243 - Improvement in session reading performance.
  • JLT-170568 - Fix a potential ChannelClosedException during session reading.

Mobile

  • JLT-166563 - iOS Agent: reported invalid battery level
  • JLT-170108 - Android Agent: VerifyError on Android 5.0+ devices when auto-instrumentor property DTXBKSPassword (or cpwrUEM_startup.bksPassword) is used
  • JLT-170551 - Android Agent: Updated Android build tools for supporting Android 7.0 feature (requires Java 1.8)

Collector

  • JLT-168703 - Java 8 instrumentation can lead to NoSuchMethodExceptions with serialized lambda expressions.
  • JLT-169011 - Added ability to skip DB Agent permission checks via boolean debug flags.

UEM

  • JLT-168828 - Documents which are exported via PureLytics Stream will be dropped if the contain '.' in field names
  • JLT-170028 - Fix evaluation of mobile web request measure (only worked with contains)

6.3.14.1011 Resolved Issues

Most important issues since the last public updates

UEM

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

All resolved issues

UEM

  • JLT-144672 - If dojo.ready is called without a function argument, the JavaScript agent increases the loadMarkers, but never decreases it. This leads to a load action which never ends and run into a timeout.
  • JLT-165744 - only dtAdkTag cookies ending with _0 are ignored now instead of ignoring all ending with 0
  • JLT-166515 - World Map dashlet: Fixed filtering by application when displaying active visits.
  • JLT-167670 - AngularJs module does not invoke correct multiple success callbacks
  • JLT-168659 - Improved details for browser warnings related to actions that time out.

Server

  • JLT-150899 - Baseline Incidents ignoring incident severity setting
  • JLT-165213 - Storing EndUserErrorRecords in the PWH may cause out-of-memory situations on the server

Client

  • JLT-163692 - Warning about default shipped server certificates was updated.
  • JLT-169113 - Most empty charts would not be rendered at all.

ServerCorrelation

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

PWH

  • JLT-168706 - Frontend Server log contains unique constraint violation exceptions

NGINXAgent

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

6.3.13.1013 Resolved Issues

Most important issues since the last public updates

JavaAgent

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

All resolved issues

WebserverAgent

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

DotNETAgent

  • JLT-147682 - Move Autosensor Thread to native to fix a deadlock problem with multiple AppDomains (e.g. Hanging HTTP-Requests in IIS)

Mobile

  • JLT-164114 - Deadlock on main thread if iOS Mobile Agent is used with Google Analytics and Google AdMob.
  • JLT-164450 - Android instrumentation fails with NullPointerException: handle debug info optimization by dexguard 7.0

Server

  • JLT-165617 - Sessions and resource dumps are now bulk deleted when storage limits are reached.
  • JLT-165681 - Add 2nd chance for reading firstNode of a Path and additional log output when running into a specific error situation during session reading.
  • JLT-165405 - User gets NPE in client on loading PPs or transaction flow due to dbagent data and lack of permissions
  • JLT-164881 - Incidents don't show up in heat field due to ArrayIndexOutOfBoundException in TransactionPattern
  • JLT-159566 - Resource dumps are deleted now even if there is still enough storage space available. Not enabled per default!

JavaAgent

  • JLT-161297 - Elastic search sensor causes java.security.AccessControlException
  • JLT-165222 - Application detection ignores request query.

UEM

  • JLT-154089 - Memory leak in JS Agent core with IE Compatibility Mode.

6.3.12.1013 Resolved Issues

2 critical issues since the last public update

WebUI

  • JLT-141781 - Sometimes dashboards cannot be edited anymore by the owner.
    • Impact: In some curcumstances dashboards cannot be edited anymore.
    • Cause: Dashboard owner name is not handled case-insensitive.
    • Solution: User name in dashboard context is now checked case insensitive.

UEM

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

16 other issues since the last public update

WebserverAgent

  • JLT-158274 - Webserver agents unnecessarily avoid using the POSIX timer and reinitialize the selected timer also on unrelated configuration updates.
  • JLT-158261 - Webserver agents cannot access POSIX timer functions on some systems forcing the agent to use a fallback timer.

Collector

  • JLT-159395 - Collector Not Accepting New Agent Connections.

UEM

  • JLT-164571 - UEM error handling module not returning event handling functions correctly
  • JLT-163323 - JS Agent's Basic XHR module doesn't fire readystatechange event on IE 10 and lower if listener is registered after call to "open".
  • JLT-158259 - Fixed "Failed to parse mobile tag" log spam: fixed handling of mobile tag, if PurePath is not started by sensor reading the tag.
  • JLT-161403 - Named functions in 'javascript:' also trigger a fake beforeunload event causing actions to time out

MainframeAgent

  • JLT-159647 - zRemoteAgent sends an unnecessary full reconnect message when a sensor configuration is updated.

Mobile

  • JLT-164364 - Rare deadlocks on main thread with iOS Mobile Agent on iOS 10.

PWH

  • JLT-164335 - Performance Warehouse Exception Incidents are never closed

Server

  • JLT-149666 - GC Health State calculation is completely off on multicore processors
  • JLT-160561 - Allow to disable following unknown downlinks during analyzer runs to improve analyzer performance via DebugFlag. Also never try to find a referenced path that has been disposed before storage.

JavaAgent

  • JLT-157468 - java.lang.ObjectInputStream is excluded from instrumentation on Java 8 and newer.
  • JLT-162228 - Application detection ignores host headers on servlet sensor.

Client

  • JLT-163911 - Dynamic Measure Matrix passes incorrect application filter when using "Show in Dashboard"
  • JLT-162603 - Dynatraces client freezes when using the chart dashlet with a small timeframe that lies far in the past (where high resolution data is no longer available).

6.3.11.1016 Resolved Issues

All resolved issues

ServerCorrelation

  • JLT-164257 - Fixed a UEM correlation bug (PurePaths did complete late) introduced by JLT-157469
  • JLT-163338 - Add more detailed log output if a node would be added to a complete path.
  • JLT-162101 - Web request response time is unreliable when subpath contains async servlet processing

Client

  • JLT-145699 - Opening the Dashlet Properties under some cirumstances caused the resulting dialog to stay empty.
  • JLT-163180 - Error dashlet - Detail panel: Order by User Action column not working
  • JLT-117603 - Drill-down from failure rate measures within charts does not work

WebserverAgent

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

Server

  • JLT-157469 - Avoid global agent time impact of agents that do not contribute to PurePaths
  • JLT-158483 - Dynamic Measure Matrix - Bar visualization doesn't change color with threshold violation for host measures

Collector

  • JLT-159941 - Monitors create unexpected host splittings for measures after server restart.

UEM

  • JLT-163140 - Abort event is fired two times if registered onto an instrumented XMLHttpRequest object via the "onabort" property.
  • JLT-159138 - Webrequests are incorrectly linked to actions that are already complete if no page change occurred for at least 15 minutes.
  • JLT-162477 - JavaScript exception with perceived render time module if images are removed during onload phase.

JavaAgent

  • JLT-155878 - Cassandra sensor added support for new cassandra server up to 3.7
  • JLT-162322 - Cassandra agent isn't detected as NoSQL TechType

NGINXAgent

  • JLT-159508 - Nginx agent causes requests to hang when used together with Nginx's auth_request module.
  • JLT-160365 - Nginx agent occasionally truncates responses that were cached and then expired.

PHPAgent

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

MainframeAgent

  • JLT-162091 - If the zRemoteAgent is bounced with zIIP enabled, the zLocalAgent doesn't always reconnect properly, leaving CICS/IMS subagent disconnected.

6.3.10.1010 Resolved Issues (465 total)

4 critical issues since the last public update

UEM

  • JLT-162088 - AngularJs error reporting does not truncate error log in 6.3
    • Impact: Beacon signal hits 32k limit
    • Cause: Not deferring to the core error handling functionality
    • Solution: Defer to the core error handling functionality which truncates error messages to 300 characters

Server

  • JLT-158226 - Community credentials validation fails for non-ascii characters
    • Impact: Not able to authorize at eServices
    • Cause: eServices switched to using ISO-8859-1 encoding for authentication, but the http client did use US-ASCII
    • Solution: Switched to ISO-8859-1 encoding for authentication headers
  • JLT-160542 - Host names or system profile names containing dots may cause "testruns" REST API endpoint to return incorrect href for newly created testrun.
    • Impact: Wrong href generated may cause REST API clients to fail when testrun data is requested.
    • Cause: Regex matching type extension in the whole request URL also matches dots in host and system profile names.
    • Solution: Fixed regex to match type extension only at the end of the URL.

HostAgent

  • JLT-159571 - Agent restart from agents overview does not work anymore.
    • Impact: Restarting agent is not working.
    • Cause: Service instance was not resetted before restart.
    • Solution: Clear service instance for being clear to restart agent.

13 other issues since the last public update

PWH

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

HostAgent

  • JLT-144112 - Changing warning log to info in case agent version file cannot be stored, as failing to store agent version file is not a critical issue."
  • JLT-157817 - Webserver master agent: Not shutting down properly when service is disabled while running.

Server

  • JLT-161246 - Improved debug logging for permission check failures.
  • JLT-161064 - Add crossframe scripting prevention mechanisms (tabbed HTML Reports).
  • JLT-159475 - Fix Postprocessing of Memory Snapshot with a remote AnalysisServer leaves raw file on disk and does not update size correctly in SessionManager.
  • JLT-157434 - Prevent reflected file download by adding filename to Content-Disposition header.
  • JLT-160157 - Add crossframe scripting prevention mechanisms (HTML Reports).
  • JLT-157433 - Add crossframe scripting prevention mechanisms (HTTP Header X-Frame-Options, Framebusting JS).
  • JLT-159557 - oneagent doesn't receive configuration if agent auto update is disabled
  • JLT-159296 - fix log spam when uem config can't be loaded
  • JLT-151359 - Selenium tests not recorded if test name does not contain dot

Collector

  • JLT-160403 - Fix collector disconnect when adding/removing sensor rule from the PurePath dashlet and pressing "Open Hierachy"

6.3.9.1009 Resolved Issues

1 critical issues since the last public update

UEM

  • JLT-159259 - Basic XHR Detection causes JavaScript agent to append "application/xml" Content-Type header to XHRs where XML nodes are sent.
    • Impact: Some browsers don't care about a Content-Type header already being set on an XHR and append other properties to the already existing header. This can lead to header-parsing errors on the webserver.
    • Cause: Due to a weird behaviour older IEs show when sending XHRs with xml content, the agent implemented a workaround to normalize this behaviour across browsers by setting a Content-Type header.
    • Solution: Removing the normalization process on the JavaScript agent stops it from appending another Content-Type header.

18 other issues since the last public update

Collector

  • JLT-159536 - java.lang.VerifyError is thrown when com.ibm.mq.MQQueueManager.getName() is overriden.
  • JLT-159504 - Instrumentation of Java 8 applications might result in a IllegalAccessError being thrown during the first startup.
  • JLT-157631 - Elapsed times are incorrect after a mainframe subagent reconnect.

JavaAgent

  • JLT-152580 - Partial instrumentation of java 8 applications might result in IllegalAccessError.
  • JLT-157737 - calling instrumented method in a thread's hashCode method causing endless recursion

ServerRTA

  • JLT-158966 - Null pointer check added in Rate Measure calculation for charting

Mobile

  • JLT-159257 - UIStatusBar overlays UINavigationController if subclassed.
  • JLT-159057 - change default value for cellular carrier to "-"

Client

  • JLT-159271 - REST-Call generates many warnings in server logfile
  • JLT-158792 - Method Hotspots Dashlet can use a lot of memory due to no Result Limit being considered for Details.
  • JLT-159108 - Android instrumentation wizard with webstart client on Windows
  • JLT-157974 - The listener responsible for the selection was not registered to all required controls only affecting Mac OS X.

Server

  • JLT-159394 - Transaction flow sometimes doesn't calculate times correctly for callers of external services.
  • JLT-158093 - (Infrastructure)Exclusion rule with ignore doesn't influence host health status (only host health history)
  • JLT-156597 - Fix problem during session reading from many stored sessions caused by too small LRU cache size

UEM

  • JLT-154926 - Perceived Render Time module doesn't capture images if they are loaded too quickly.
  • JLT-159111 - HTML injection wouldn't find a suitable injection location in certain cases involving <script> tags before <html>.

WebUI

  • JLT-158204 - Error in world map: "Invalid user experience data"

6.3.8.1016 Resolved Issues

2 critical issues since the last public update

Server

  • JLT-158328 - Directly connecting the client to the backend server causes a protocol error.
    • Impact: The client was not able to correctly initiate a session directly to the backend server.
    • Cause: The client was waiting for a value when directly connecting to the backend server which was never received.
    • Solution: When the connection is directly initiated from the client to the backend server, the expected value is transmitted and thus a successful session handshake can be completed.
  • JLT-152870 - MQ Mapping Update seems to slow down dynaTrace Server Settings dialog load time.
    • Impact: Doing a consistency check with every read-in of the file mqmappings.xml may cause severe time delays opening the server configuration at the clinet, if the file holds lots of MQ mapping data.
    • Cause: Consolidation check of mapping is done at every read of the file mqmappings.xml, which holds besides the MQ mapping data the MQ tagging options, which are presented in the client dialog for the server configuration.
    • Solution: The consistency check is not done anymore when the mqmappings.xml is read (as the file must not be changed by hand anyway). It is only called when the server gets an update via REST interface of mapping data reported by MQ mapping tool. This update is the only way to change/update the MQ mapping data, so its safe to put the consistency check to this very place. Note: For future releases (v7.0ff) it is already in discussion to use the mqmappings.xml file sole for MQ mapping data and put the MQ tagging flags to the server configuration files, where they correctly belong to. This will avoid the unnecessary reading of MQ mapping data at the client side at all.

23 other issues since the last public update

Server

  • JLT-147374 - Fix a NullPointerException during class-cache cleanup
  • JLT-158971 - Possible NullPointerException when fetching DB Agent information from Collector.
  • JLT-158667 - Fix a NegativeArraySizeException that happens when a path is stored that has more than 32k linked paths.
  • JLT-157587 - Infrastructure dashboard: Host don't show any host health history and are incorrectly shown as offline for user with limited rights
  • JLT-157916 - Fix a concurrency problem during Visit storage
  • JLT-157997 - Updated apache commons collections from 4.0 to 4.1 which contains security issues.
  • JLT-141978 - Incident "Application Process Shutdown" incorrectly thrown when agent connects to another collector in collector group
  • JLT-153674 - Lock contention with heavy usage of custom tagging

Communication

  • JLT-152848 - Newly installed Collectors may run into a connection timeout when getting agentres files from a often updated Server

Client

  • JLT-158654 - Re-enable automatic reporting of error-detection details that has been removed with 6.3.6 upon debug-flag
  • JLT-148901 - JMX/PMI browser performs undesired changes to user defined measure names, also changes names of measures already known by dtserver without following rename protocol.
  • JLT-154735 - Old Client is not upgraded if a public update is active on the Server

UEM

  • JLT-158825 - Updated UEMDatabases from version 0.1.9 to 0.2.4
  • JLT-157693 - javascript:void(0) clicks in IE compat mode trigger beforeunload event causing actions to timeout
  • JLT-136748 - Bandwidth: Incorrect bandwidth or latency calculations, caused by download images rejected by browser.
  • JLT-157445 - Fix latency calculation during mobile correlation for mobile actions with only one very long lasting web request.

MainframeAgent

  • JLT-156260 - Mainframe.release property is not being sent on subagent registration. This may cause the Mobile Workload dashlet to fail.

WebUI

  • JLT-157681 - Improved logging for world map which only showed a generic error message in the UI.

Mobile

  • JLT-155911 - iOS Added support for NSProxy based delegates for supported UIControls.
  • JLT-156831 - show correct DTXMultidexMoveMethodCount value in auto-instrumentor log

WebserverAgent

  • JLT-157796 - Restarting a webserver while the webserver master agent is not active unexpectedly deactivates handling of JS agent monitor signals.

JavaAgent

  • JLT-150029 - Add signoff-for-reconnect message to agent communication

ServerRTA

  • JLT-142975 - Optimized realtime-analysis for setups with high number of Business Transactions and/or high UEM load.

6.3.7.1007 Resolved Issues

Most important issues since the last public updates

MainframeAgent

  • JLT-155864 - zRemoteAgent disconnections and lack of reconnects when the zDC task is cpu-starved
    • Impact: The zLocalAgent never reconnects, so the subagents never reconnect.
    • Cause: Since the zDC (and zLocalAgent) can't get enough cpu, they don't respond timely, and aren't notified correctly
    • Solution: Up the priority of the zDC task, and fix the zLocalAgent to recognize this scenario.

Server

  • JLT-156532 - Collector receives malformed input from server and closes connection
    • Impact: Collector closes connection
    • Cause: Server sends wrong protocol to collectors with a version less than 6.3
    • Solution: Fix protocol for collectors with a version less than 6.3

JavaAgent

ServerCorrelation

  • JLT-157102 - Fixed a ConcurrentModificationException in the correlation service occurring when a agent connects while active memory management forces a buffer reduction.
    • Impact: In one specific case the proportion of discarded PurePaths started to increase until they reached 100 percent.
    • Cause: Missing synchronization led to this ConcurrentModificationException.
    • Solution: Added synchronization in the DynatraceCorrelationService during cleanup and creation of the correlation engine.

All resolved issues

Client

  • JLT-157305 - NullPointerException occured in update dialog, when server was shutdown before restart through wizard has been initiated.
  • JLT-157488 - NPE may occur when a server is offline during configuration of another server.
  • JLT-155498 - Wrong abbreviation of .NET nodes with generics in PurePath or Method Hotspots dashlets.

MainframeAgent

  • JLT-155864 - zRemoteAgent disconnections and lack of reconnects when the zDC task is cpu-starved
  • JLT-153738 - Elapsed times for Mainframe agent purepaths are not accurate.
  • JLT-153953 - IMS Configurations are not recognized when IMS regions register with the dynatrace collector.
  • JLT-154052 - Possible zRemoteAgent crash while fetching zLocalAgent log files
  • JLT-154298 - Possible zRemoteAgent crash under extreme load, due to a disposed provider
  • JLT-154577 - Possible zRemoteAgent crash under extreme load, if sequence errors are present

UEM

  • JLT-157367 - Endless loop in EUEMobileCorrelationCore during linking web requests to mobile lifecycle events caused server restarts.
  • JLT-152591 - Fixed displaying W3C resource timings for UEM only actions
  • JLT-155910 - JQuery module throws exceptions on older IE browsers with older jQuery versions (<1.4.4) if statusText is accessed too early.

Collector

  • JLT-157464 - Adding DebugFlag for JLT-148771 (BeginRequest causes Seperate PurePath); activate feature using "com.dynatrace.diagnostics.collector.enableAspNetBeginRequestTagging" on collector.

Server

  • JLT-147953 - A drilldown on the entry screen to web requests did not return any data due to wrong handling of filter.
  • JLT-155743 - Severity of predefined incidents does not correspond to configured severity.
  • JLT-157292 - Error during session reading when a PurePath without any Node is written into a session.
  • JLT-153314 - PurePaths don't complete successfully because method metadata cannot be retrieved from the collector in case of communication issues.
  • JLT-156532 - Collector receives malformed input from server and closes connection
  • JLT-157084 - Increase a LRU map size to prevent session-reading problems with linked paths / visits.
  • JLT-156605 - Added missing metrics for WebAPI tests (Remoting call count, Webservice call count, Webrequest call count, PurePath CPU duration, PurePath duration without suspension).
  • JLT-154283 - Renaming of Business Transactions and Measures fails after updating to 6.3.4.
  • JLT-155966 - Ignore Global Agent Time calculation for zRemoteAgent master to prevent drift issues.

JavaAgent

  • JLT-154598 - Added the hasidletimebug Agent option as a linux kernel bug workaround for high cpu i/o wait times.
  • JLT-157159 - Fix NoSuchMethodError when agent <6.0 connects to collector >=6.0 with cassandra sensor enabled

ServerCorrelation

  • JLT-157102 - Fixed a ConcurrentModificationException in the correlation service occurring when a agent connects while active memory management forces a buffer reduction.

Mobile

  • JLT-157114 - iOS XcodePlugin needs to resolve relative path when downloading ADK.

PWH

  • JLT-154588 - Dynatrace Server cannot connect to performance warehouse on SQLServer with SSL

ServerRTA

  • JLT-156454 - Correct calculation of measure Time of Web Requests for sub paths

Plugins

  • JLT-15653 - Duplicate of JLT-156532.

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.

 

 

  • No labels