Skip to end of metadata
Go to start of metadata

2016-04-25 

This update levels up Web dashboards, speeds up the way how you create them and improves your user analytics with better UEM workflows.

        Get 6.3 for SaaS

Web dashboards for large screens

More content - more power - but lightweight at the same time. Now ready to use as your primary solution for your operational dashboards. Created on your iPad, shown at your weekly status report, and permanently up on your large monitoring screens to keep you in touch with your apps and environment.

  • Make your dashboards more effective. Up to eight columns of dashboard tiles allow you use the real-estate of your screen much more effectively.
  • Creating dashboards just became much faster. Clone dashboard tiles you've already configured.

Level up your business analytics!

  • Worldmap and PureLytics are now connected. If you spot a problem in a certain region - drill down if your recent deployment causes issues for some users.
  • The improved omnichannel now covers the complete spectrum of visits to your pages including Robots and Synthetic.

 Upgrading and Getting Started With This Release

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

 Resolved and Known Issues

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