Skip to end of metadata
Go to start of metadata

2016-03-21

 

The first update for Dynatrace AppMon 6.3 has been released! This update contains critical fixes and improvements. You are able to perform a controlled update without any migration! Recommended for all users!

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

 

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