Discussion Feed

Issue When trying to start the Machine Agent with server visibility, you are seeing the exception below: [extension-scheduler-pool-4] 26 Jun 2018 12:32:06,394 ERROR RawCollectorUtil - Could not collect raw data com.fasterxml.jackson.databind.JsonMappingException: No content to map due to end-of-input at [Source: ; line: 1, column: 0] at com.fasterxml.jackson.databind.JsonMappingException.from(JsonMappingException.java:270) at com.fasterxml.jackson.databind.ObjectMapper._initForReading(ObjectMapper.java:3854) at com.fasterxml.jackson.databind.ObjectMapper._readMapAndClose(ObjectMapper.java:3799) at com.fasterxml.jackson.databind.ObjectMapper.readValue(ObjectMapper.java:2858) at com.appdynamics.sim.agent.extensions.servers.collector.RawCollectorUtil.runCollector(RawCollectorUtil.java:199) at com.appdynamics.sim.agent.extensions.servers.collector.RawCollectorUtil.runCollector(RawCollectorUtil.java:131) at com.appdynamics.sim.agent.extensions.servers.model.solaris.SolarisRawCollector.collectRawData(SolarisRawCollector.java:81) at com.appdynamics.sim.agent.extensions.servers.model.solaris.SolarisRawCollector.collectRawData(SolarisRawCollector.java:40) at com.appdynamics.sim.agent.extensions.servers.model.Server.collectAndReport(Server.java:61) at com.appdynamics.sim.agent.extensions.servers.ServersDataCollector.run(ServersDataCollector.java:90) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang. Thread .run( Thread .java:745) [AD Thread -Metric Reporter1] 26 Jun 2018 12:32:06,401 DEBUG ManagedMonitorDelegate - REST Sending Binary payload Size : 226 bytes [extension-scheduler-pool-4] 26 Jun 2018 12:32:06,408 ERROR RawCollectorUtil - The standard out from the collector script was: [extension-scheduler-pool-4] 26 Jun 2018 12:32:06,408 WARN RawCollectorUtil - The error log from the collector script was: bash: line 739: syntax error near unexpected token ` "," ' bash: line 739: ` [ $print_comma -eq 0 ] && print_comma=1 || jsonStringsArr+=( "," )'   Solution Validate your Bash version using command below: bash -version   The Bash version should be at least 3.1. Specifically, you will need a Bash version that supports arrays. Upgrading the Bash version and restarting the Machine Agent should resolve this. ... View more

Table of Contents Issue Enabling Flash Additional Recommendations   Issue When clicking on certain screens in the Controller (e.g., Analytics → Configuration), you may encounter the message "Please install Flash to use this feature" in the top right corner. This is due to the fact that a few screens in the Controller UI leverage Flash and require Flash Player 10 or greater. AppDynamics recommends version 11.   This behavior may be noticed in all browsers, but the steps in this article are specific to Chrome.   We recommend that all customers using the latest version of Chrome enable Flash.   Please note that it’s a top priority for AppDynamics to remove Flash from the product and work is currently in process. Watch for announcements in our monthly Product Updates.   Enabling Flash In the latest versions of Chrome, your Flash settings will be overridden every time you restart your browser. Please follow the instructions below to enable Flash in your specific Chrome version: Chrome v70 Chrome v71   Chrome v70 If you are using Chrome v70, the steps below guide will you through how to enable Flash permanently so you don’t need to enable it each time you launch Chrome.   1. Open Chrome 2. Go to: chrome://flags/ 3. Search for: Enable Ephemeral Flash Permissions 4. Change its value to: Disabled 5. Restart Chrome 6. Go to: chrome://settings/content/flash 7. Click on Allow - Add button 8. Add site: https://[*.]saas.appdynamics.com 9. Restart Chrome   Chrome v71 The Enable Ephemeral Flash Permissions feature mentioned above is not available in Chrome v71. If you quit Chrome, your Flash settings won’t be saved. You will need to re-enable Flash each time you load your browser. To enable Flash, follow the steps below:   1. Browse to your AppDynamics Controller. 2. Click the drop-down menu to the left of the URL bar (typically a lock icon). 3. Set Flash settings to Allow . (Note: If you don’t see the Flash setting, click Site Settings and you will see the option to enable Flash) 4. Reload the page. 5. If you close and restart the browser, you will need to complete these 4 steps above again.   Additional Recommendations As a best practice, we also recommend disabling AdBlock when using the Controller UI to avoid issues loading particular screens. For instructions, see: How do I disable AdBlock in Chrome? ... View more

Question How do I instrument Apache Tomcat on CA Project Portfolio Management (Clarity PPM)?   Solution L aunch the NSA console  Navigate to CSA properties -> Application tab Under "Application Server" select Apache Tomcat as the vendor and edit the Java VM parameters as follows: Add AppDynamics Agent entry:   -javaagent:<agent_home>/javaagent.jar   For more information: Load the Java Agent in a JVM      Last updated: 2/20/19 (updated product name) ... View more

After upgrading or installing AppDynamics version 4.3.x, users may see the following error  when accessing the "Servers" tab in the Controller UI.   Error: The requested URL /controller/restui/userPreferenceManager/setGeneralUserPreference/SIMMachinesListController-stateId--SIM_MODE-4.3-metricToggles/[{"selected":false,"label":"Availability (%)","type":0,"metricName":"Hardware Resources|Machine|Availability"},{"selected":false,"label":"Availability (%) Trend","type":1,"metricName":"Hardware Resources|Machine|Availability"},{"selected":true,"label":"CPU (%)","type":0,"metricName":"Hardware Resources|CPU|%Busy"},{"selected":true,"label":"CPU (%) Trend","type":1,"metricName":"Hardware Resources|CPU|%Busy"},{"selected":false,"label":"CPU Steal (%)","type":0,"metricName":"Hardware Resources|CPU|%Stolen"},{"selected":false,"label":"CPU Steal (%) Trend","type":1,"metricName":"Hardware Resources|CPU|%Stolen"},{"selected":true,"label":"Disk I/O (%)","type":0,"metricName":"Hardware Resources|Disks|Avg IO Utilization (%)"},{"selected":true,"label":"Disk I/O (%) Trend","type":1,"metricName":"Hardware Resources|Disks|Avg IO Utilization (%)"},{"selected":true,"label":"Disk Usage (%)","type":0,"metricName":"Hardware Resources|Volumes|Used (%)"},{"selected":true,"label":"Disk Usage (%) Trend","type":1,"metricName":"Hardware Resources|Volumes|Used (%)"},{"selected":false,"label":"Load - 1min","type":0,"metricName":"Hardware Resources|Load|Last 1 minute"},{"selected":false,"label":"Load - 1min Trend","type":1,"metricName":"Hardware Resources|Load|Last 1 minute"},{"selected":true,"label":"Memory (%)","type":0,"metricName":"Hardware Resources|Memory|Used %"},{"selected":true,"label":"Memory (%) Trend","type":1,"metricName":"Hardware Resources|Memory|Used %"},{"selected":false,"label":"Memory Swap Used (%)","type":0,"metricName":"Hardware Resources|Memory|Swap Used %"},{"selected":false,"label":"Memory Swap Used (%) Trend","type":1,"metricName":"Hardware Resources|Memory|Swap Used %"},{"selected":true,"label":"Network I/O (%)","type":0,"metricName":"Hardware Resources|Network|Avg Utilization (%)"},{"selected":true,"label":"Network I/O (%) Trend","type":1,"metricName":"Hardware Resources|Network|Avg Utilization (%)"}] was not found on this server.   Screenshot:   The cause of this issue is due to some versions of Apache being unable to parse slashes in POST query parameters.   As of version 4.3, the view options are persistent for users. To do this, AppDynamics keeps track of what tab the user selected last time using an API call. This is a POST request, with query parameter of '/' which cannot be parsed by Apache, unless it is defined in the config file.   The solution is to turn on the AllowEncodedSlashes NoDecode  option in the Controller server's Apache config file ( httpd.conf) .   For more information, see this Stack Overflow discussion: Need to allow encoded slashes on Apache   ... View more

When creating database custom query metrics, if the queries are complex, they may return a timeout error message in the Database Agent logs.    For example from DB2 database:   Caused by: com.ibm.db2.jcc.am.SqlTimeoutException: DB2 SQL Error: SQLCODE=-952, SQLSTATE=57014, SQLERRMC=null, DRIVER=4.16.53   As a solution, a user can increase the timeout parameter by adding the following property in the DB Agent startup file, or as a system argument if DB Agent is started through a command prompt or terminal.    -Ddbagent.custommetric.query.timeout.seconds=<time_in_second>    Example: -Ddbagent.custommetric.query. timeout.seconds=120     ... View more

To set up a Java Agent to automatically give unique names to nodes for the application, add the following element to the /conf/controller-info.xml file.   <auto-naming> true </auto-naming>     Example using a 4.2.14.0 Agent:   Add the following element to the /AppServerAgent-4.2.14.0/ver4.2.14.0/conf/controller-info.xml file: <auto-naming>true</auto-naming> Restart the JVM. Node names will be listed as null in the Controller UI until the server is started. Naming convention is  application_server@host . ... View more

Problem: When a non-admin user runs automatic leak detections (ALD), object instance tracking(OIT), or Custom memory structures, they may see the following error:   The current user 'ABC' does not have permission to do this. (action: CONFIG_AGENT_PROPERTIES entity: APPLICATION_COMPONENT_NODE 235) (agentManager.updateAgentConfiguration)   Solution: An administrator must edit the Agent permission and role properties. The name of the permission can be extracted from the error message.   Example:   ... View more

When running WebSphere with Security Enabled, the user must provide permissions to the Java Agent, to ensure a seamless  interaction between the two.   Add the following snippet to the security policy file:   grant codeBase "file:\* AGENT_DEPLOYMENT_DIRECTORY \*/-"   {      permission java.security.AllPermission; };   The security policy file is located in the AppDynamics Agent logs under JVM arguments:     -Djava.security.policy=...../security.policy   Or Unix users can use the ps command to find the command line parameters for the JVM.   If the JVM argument is not provided, the application may be using a default Java policy file ( java.policy ). Add the previously mentioned snippet to this file.    Examples where applying permissions is not sufficient:   1. Agent logs show: java.security.AccessControlException: access denied ("java.io.FilePermission" "/xx/xx/xx/y.xml" "read")   grant codeBase "file:\* AGENT_DEPLOYMENT_DIRECTORY \*/-"  {    permission java.security.AllPermission;    permission java.io.FilePermission "*","read,write,execute";  };   2. Agent logs show:  java.security.AccessControlException: access denied (java.lang.RuntimePermission getClassLoader)   grant codeBase "file:\* AGENT_DEPLOYMENT_DIRECTORY \*/-"  {  permission java.security.AllPermission;  permission java.lang.RuntimePermission "getClassLoader"; };     3. Agent logs show: java.security.AccessControlException: access denied ("javax.management.MBeanServerPermission" "findMBeanServer")   grant codeBase "file:\* AGENT_DEPLOYMENT_DIRECTORY \*/-"  {  permission java.security.AllPermission;  permission javax.management.MBeanServerPermission "findMBeanServer"; };  Note: Replace  \*AGENT_DEPLOYMENT_DIRECTORY\* with the Agent home directory path. Do not miss the forward slash (/-) at the end.    Linux example:  grant codeBase "file:/opt/appdynamics/appserveragent/-" Windows example:  grant codeBase "file:c:/appdynamics/appserveragent/-"                    Additional solutions:    Add the following property as a JVM argument only on development instances. Remove this property as soon as security debugging is completed.  -Djava.security.debug="access,failure"   Additionally, create a node level property, which can coincide with the above security policy file changes.   Node property example: property name: enable-interceptors-for-security type: boolean value: true   Note:  Changes in the security policy file require a JVM restart.    ... View more