Known Issues

Key Product Summary Affected Version(s) Fix Available In
JAVA-14157 Java Agent

Under certain conditions, memory leak might occur when monitoring transactions initiated by messages from queues such as Kafka, Tibco, and WebSphere MQ.

Workaround: Disable JMS Transaction Monitoring. This will result in loss of visibility into message queue transactions. This issue is resolved in version 25.10. It is recommended to upgrade to version 25.10 or later.

 25.7, 25.8, and 25.9 25.10
CON-7279 Controller The registered JMX entities block the agent registration leading to thread pool saturation. 25.7.5 -
CON-7378 Controller The tags are missing for Servers even though it is visible on the Network tab. To workaround this issue set entity.tagging.enabled to false. 25.10 -
CON-7417 Controller The tag creation fails because of permission errors. 25.7.0 -

  • CON-7426

  • CON-7434

 Controller The HTTP thread pool saturation causes Controller UI downtime.
  • 25.10.2
  • 25.10.0
 -
CON-7279 Controller The registered JMX entities block the agent registration leading to thread pool saturation. 25.7.5 -
CON-7378 Controller The tags are missing for Servers even though it is visible on the Network tab. To workaround this issue set entity.tagging.enabled to false. 25.10 -
CON-7417 Controller The tag creation fails because of permission errors. 25.7.0 -

CON-7426

CON-7434

 Controller The HTTP thread pool saturation causes Controller UI downtime.
  • 25.10.2
  • 25.10.0
 -
COSMOSX-2988 Smart Agent Smart Agent may cause port exhaustion, which prevents remote access to Windows servers 25.10.0 25.12.0
COSMOSX-2803 Smart Agent

The rollback action fails for the supported agents.

Workaround: Install agents within a dedicated subdirectory (such as, C:\appdynamics\<agent> or /opt/appdynamics/<agent>), rather than installing directly at the root of the file system.

 25.10.0 25.12.0
COSMOSX-2760 Agent Management

Machine Agent extensions are not copied during an upgrade using the Smart Agent.

Workaround: Upgrade to Smart Agent 25.10 and Controller 25.10.0.

 25.4.0 -
DBMON-11480 Database Agent

Database Agent cluster discovery fails on SQL Server versions earlier than 2017 because the sys.dm_os_host_info Dynamic Management View (DMV) is not supported.

 25.4.0 25.10.0

UI-9520

 Controller

Controller gives an error while exporting the metric browser data. This issue occurs only when the local time zone is selected under Username > My Settings > My Preferences.

Workaround:

Navigate to Username > My Settings > My Preferences > View Preferences > Display Time Zone, and select any other time zone than your local time zone.

 25.10.0 -

IAM-7355

 Accounts
When you navigate to Settings > Administration > Authentication Provider > SAML Group Mappings and perform the following actions in the Mapping of Group to Roles
  • Add a new group and assign a role. Save both the popup and the main page.
  • Edit an existing group and update the group name by changing only the letter case. For example, changing "TEST_NAME_3" to "TEST_NAMe_3", then save the changes.

AppDynamics does not retain the edited SAML group if the update involves only letter case changes. After saving, the group is removed from the mapping list, and all associated role mappings are lost.

Workaround:

To update a group name with only a case change:
  1. Delete the existing group-to-role mapping for the group you wish to modify.
  2. Add a new group-to-role mapping using the desired case for the group name.
  3. Reassign the roles that were previously mapped to this group.
Note: This issue is specific to group name changes involving letter case only. Renaming a group entirely does not trigger the issue.
25.10.0 -

LIC-6479

Licensing

For a license rule, when you define an application scope that equals to or contains a specific string and select the Dynamic option, the Controller UI displays all the application names matching the condition, ignoring the uppercase and lowercase differences.

However, the license rule itself is applied in a case-sensitive manner. The rule only affects applications whose names match the specified condition exactly as typed, considering the uppercase and lowercase letters.

Example:

Suppose you have the following applications: Xyz1, Abc1, Abc2, Cba1, and Cba2.

  • You set the condition to CONTAINS a.
  • The Controller UI displays Abc1, Abc2, Cba1, and Cba2. All these names contain "a" or "A", regardless of case.
  • The license rule will only be applied to Cba1 and Cba2. These names contain a lowercase "a" exactly as specified in the condition.

  • The rule will not apply to Abc1 and Abc2, because they contain an uppercase "A", which does not match the lowercase "a".

Recommendation:

Avoid the Dynamic option when configuring Application Scope. Instead, manually select each application name individually from the list.

 >=25.7.0 -