Known solutions and workarounds

This page details a number of resolved issues and solutions to issues that have been reported to the Dynatrace Support team.


Host, Ubuntu 16.10

Issue:

Due to compile optimization changes in the C runtime packages provided with Ubuntu 16.10, new stack-alignment requirements have been introduced. OneAgent versions earlier than 1.103.237 don’t yet fulfill these requirements. Using versions of OneAgent earlier than 1.103.237 may lead to process crashes during dynamic symbol resolution (dlsym) calls in the C runtime.

Solution:

Update to OneAgent version 1.103.237 or higher. This version of OneAgent will be available to all Dynatrace environments by October 20th, 2016. Here are the instructions for upgrading OneAgent:

  1. Select Settings > Preferences from the navigation menu (only visible to environment admins).
  2. Ensure that the Automatically update OneAgent instances setting is enabled. OneAgent version 1.103.237 will be automatically deployed once it’s available on your environment. If Automatically update One Agent instances is disabled, select OneAgent version 1.103.237 or higher and click Update now.

Java, IBM J9

Issue:

In rare situations, when implementing a try-catch-finally block and catching a multi-type exception with Java 7, the exception is caught, but the source code in the finally block doesn’t execute. This issue has been fixed since IBM J9.

Solution:

Fixed since IBM J9

  • 7 R1 SR2 FP11 (7.1.3.0)

  • 7 SR9 (7.0.9.0)

  • 8 SR1 (8.0.1.0)

Source


Java, WebSphere MQ , JMS

Issue:

When using WebSphere MQ via JMS, Dynatrace isn’t always able to determine the queue name and may report the queue name as ‘unavailable’. This happens when MQ messages have not been properly mapped to JMS.

Solution

Follow the IBM documentation for mapping JMS messages onto IBM MQ messages. Once the MQRFH2 header has been properly mapped, Dynatrace will pick up the correct queue name.

Java, Oracle HotSpot/OpenJDK

Issue:

A known issue in Oracle HotSpot and OpenJDK can lead to a JVM deadlock in ThreadTimesClosure or incomplete CPU timings of background activities. Be sure to update to Oracle HotSpot 6u38/7u40 or OpenJDK 7u45 and higher to benefit from this solution.

Solution:

Fixed in Oracle HotSpot 6u38/7u40 and OpenJDK 7u45

Source Oracle HotSpot 6 Source Oracle HotSpot 7 Source OpenJDK


Java, Spring, AspectJ

Issue:

Some customers have reported the below NullPointerException during startup of their Java Spring or AspectJ applications. AspectJ has since resolved this issue, which has since been incorporated into the Spring frameworks. Simply update to Spring 2.5.4 or AspectJ 1.6 to get the fix.

Message: NullPointerException at

`org.aspectj.weaver.reflect.Java15AnnotationFindergetAnnotations
  (Java15AnnotationFinder.java:109)`

Solution:

Fixed since Spring 2.5.4/AspectJ 1.6

Source


Java/RUM

Issue:

Java applications using RUM may run into a ClassCastException upon a type cast to the implemented HttpServletRequest interface because Dynatrace replaces the original HttpServletRequest implementation with a RequestWrapper for automatic RUM injection.

Solution:

Change your source code so that it doesn’t expect a specific implementation of the HttpServletRequest interface.

Source:

n/a


UI/Docker

Issue:

With Docker versions 1.10.3 - 1.11, CPU, memory, and network container statistics are missing from the UI because data requests sent to containers via docker stats time out. Restarting Docker addresses this issue temporarily.

Solution:

Fixed since Docker 1.12. Upgrade to Docker 1.12.

Source


UI/IIS

Issue:

Due to a lack of Windows Performance Counters, the Further details tab may be not visible in the UI for IIS processes, even following IIS restart. No errors are raised during OneAgent injection.

Solution:

This can occur if there is a problem with the Performance Counter Library in the Windows Registry. To check this:

Using a Windows command, verify that the metrics are not retrievable from the Windows Registry: typeperf "\Process(w3wp*)\ID Process" -sc 15 Alternatively, use Perfmon.exe to see if data is available for the counters or to confirm that the counters don’t exist.

Consult Microsoft technical documentation to rebuild the performance libraries in the registry.

Source


.NET, IIS

Issue:

If IIS monitoring is enabled for an ASP.NET application using .NET >= 4.5 and < 4.6, in rare circumstances the application could fail with an unhandled NullReferenceException.

Message: System.NullReferenceException at

`System.Web.Security.Roles.IsUserInRole(String username, String roleName)`

Solution:

Fixed since .NET 4.6.

Source


.NET, Cassette

Issue:

Customers reported a crash when using the Cassette web asset management library.

Message: Crash at

`[TinyIoCResolutionException: Unable to resolve type: Cassette.Views.BundlesHelper]`

Solution:

As a workaround, you can use the file system as Cassette’s cache by specifying a directory in your web.config file as follows:

`<cassette cacheDirectory="App_Data\Cassette" />`

Potentially fixed in v2.4.1

Source


.NET, ConfuserEx

Issue:

Using the assembly-obfuscation tool ConfuserEx can sometimes crash .NET applications because the ConfuserEx assembly doesn’t allow “profilers” like Dynatrace.

Message: Crash at

`System.Environment.FailFast(System.String)`

Solution:

Disable ConfuserEx obfuscation or disable Dynatrace monitoring at the process level.

Source


RUM, Chrome

Issue:

Real user monitoring analysis with Google Chrome can lead to browser crashes when some resources can’t be loaded.

Message: Crash at

`window.performance.getEntriesByType('resource')`

Solution:

Until Chrome provides a fix for this issue, make sure that all resources are loaded successfully (no 301 responses) or disable W3C resource timing for third party/CDN.

To disable W3C resource timing for third party/CDN:

  1. Select Web applications from the left-hand navigation menu.
  2. Select the application you want to edit.
  3. Click the More (…) button.
  4. Click Edit.
  5. Click Content capture.
  6. Set the W3C resource timing for third party/CDN switch to Off.

Source


RUM, jQuery

Issue:

In the course of real user monitoring, failing asynchronous JQuery user actions lead to action timeouts after 180 seconds, but no error is reported. This is caused by a known jQuery limitation.

Solution:

JQuery has not provided a fix for this problem. To resolve this issue, fix the failing jQuery call on your end (for example, an AJAX request to a missing resource) or disable jQuery in XHR (Ajax) detection settings and enable basic XHR detection.

To disable JQuery detection and enable basic XHR detection:

  1. Select Web applications from the left-hand navigation menu.
  2. Select the application you want to edit.
  3. Click the More (…) button.
  4. Click Edit.
  5. Click XHR (Ajax) detection.
  6. Set the JQuery, Backbone.js switch to Off.
  7. Set the Basic XHR detection switch to On.

Source


RUM, Ext JS

Issue:

In large, complex Ext JS applications customers experienced client side response time degration like a web browser notification about an unresponsive script. Due to the internal event handling mechanism of Ext JS the application can be running slow if too many events are triggered which are captured by the RUM JavaScript agent.

Solution:

Turn off extended Ext JS event capturing in the RUM settings.

  1. Select Web applications from the left-hand navigation menu.
  2. Select the application you want to edit.
  3. Click the More (…) button.
  4. Click Edit.
  5. Click Advanced setup detection.
  6. Add exteventsoff=1 into the Custom configuration properties text field within the JavaScript library settings

If certain user actions will not be captured afterwards, use the JavaScript API to trigger actions manually.