Skip to end of metadata
Go to start of metadata

November 23th 2015

 

The next update for Dynatrace 6.2 has been released! Dynatrace 6.2.4 contains critical fixes and improvements. On top of the 6.2 release you are able to perform a controlled update without any migration! Recommended for all users of Dynatrace 6.2.

Please check out also the release notes of Dynatrace 6.2 for details on LicensingSystem Requirements and the End-of-Life Policy.

Dynatrace updates are cumulative, which means they include current and previous product changes. Therefore it's possible and supported to skip updates and install only the latest one.

 

6.2.4 Resolved Issues

Most important resolved issues since 6.2.3

Server

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

Performance Warehouse

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

All resolved issues since 6.2.3

WebUI

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

Node.js (agent unchanged)

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

Other

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

6.2.3 Resolved Issues

Most important resolved issues since 6.2.2

Client

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

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

Agent

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

Server

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

UEM

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

WebUI

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

Mobile ADK (separate download)

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

All resolved issues since 6.2.2

Server

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

Collector

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

Agents

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

Client

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

WebUI

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

UEM

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

Mainframe:

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

Other

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

6.2.2 Resolved Issues

Most important resolved issues since 6.2.1

Server

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

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

Collector

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

WebUI

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

MessageBroker

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

PHP

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

UEM

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

MobileADK

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

All resolved issues since 6.2.1

Server

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

Collector

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

Agents

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

MessageBroker

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

Client

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

UEM

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

WebUI

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

Sensors

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

Charting

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

MobileADK

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

Other

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

  • JLT-129347: node.js Update

 

6.2.1 Resolved Issues

Server

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

Collector

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

Performance Warehouse

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

Agents

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

Client

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

UEM

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

WebUI

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

Other

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

 
 
  • No labels