Discussion Feed

Hi,   We are trying to enabe Object Instance Tracking (OIT) for a Java node and we get this following message,   There is no object instance data.  This could be caused by the following reasons: [1] This feature is only supported for Oracle JVMs. It does not work for JRockit or IBM JVMs. [2] tools.jar is not in the JVM classpath. You must add it to the classpath and restart the JVM.   [1] - Yes, it is a an Oracle JVM [2] - here, does "JVM class path" refers to java.home? java.home=/ms/dist/msjava/PROJ/oraclejdk/1.8.0_162/.exec/@sys/jre   Please note the application is being run by "JDK"   The doc says  "This feature requires tools.jar to be in JRE_HOME/lib/ext. If you are running with the JDK then tools.jar will probably be setup correctly, but if you are running with the JRE you must add tools.jar to JRE_HOME/lib/ext and restart the JVM for this feature to start working"     When it says "...If you are running with the JDK then tools.jar will probably be setup correctly..", where exactly should it have been set up ?   Now, the current path for tools.jar is "\\ms\dist\msjava\PROJ\oraclejdk\1.8.0_121\lib\tool.jar"   What needs to be done to get this work? do we need to copy "\ms\dist\msjava\PROJ\oraclejdk\1.8.0_121\lib\tool.jar" to "/ms/dist/msjava/PROJ/oraclejdk/1.8.0_162/.exec/@sys/jre/lib/ext" ?   Application team doesn't want to create /lib/ext under "/ms/dist/msjava/PROJ/oraclejdk/1.8.0_162/.exec/@sys/jre" as it is a shared location.   Can someone please advise how we can get this working?   Thanks!       ... View more

Hello,   I have a healthrule suppression schedule enabled and it doesn't seem to be working as expected.   The requirement is to suppress or disable helathrule between 1 AM and 6 AM only on Sundays, and this the cron entry that i set up (see attached).   start time cron expression: * * 6 ? * 7 end time cron expression  : * * 1 ? * 7   If this is incorrect, please advise what needs to be modified. Thank you! ... View more

Hello,   We have manually configured java agent by adding the required JVM Args to a stand-alone Java App   -javaagent:/ms/dist/esm/PROJ/appdynamics-agent/4.2.11.0/java_sun_jrockit/ver4.2.11.0/javaagent.jar -Dappdynamics.agent.runtime.dir=/var/tmp/appdynamics -Dappdynamics.controller.hostName=dev-controller -Dappdynamics.controller.port=8090 -Dappdynamics.controller.ssl.enabled=false -Dappdynamics.agent.accountAccessKey=xxxxxxxx -Dappdynamics.agent.accountName=customer1 -Dappdynamics.agent.nodeName=ivapp-dip -Dappdynamics.agent.tierName=dip-Tier -Dappdynamics.agent.applicationName=DIP-DEV   We could see the agent started successfully message in the agent log. However, can't see the agent reporting to the controller. A batch job invokes the application process. appdev team says, the job every time starts the process also restarts JVM   Wondering, why we still couldn't see the agent reporting to the controller   Thanks! ... View more

Hello,   we couldn't see a couple of nodes under a specific tier (can see only 2 nodes out of 4). I can see config.xml is updated on these 2 missing hosts. This is a .NET App   Tried to restart appdynamics agent service followed by app pool recyle, which didnt help.   When look in to the agent log , i see ....."Error MachineAgentManager Metrics Maximum metrics limit reached [200] no new metrics can be created. This exception will not repeat until restart.Exception: com.appdynamics.ee.agent.commonservices.metricgeneration.metrics.spi.qe: Maximum metrics limit reached [200] no new metrics can be created. This exception will not repeat until restart"   Log excerpt :   "2017-09-27 15:57:58.2744 163472 AppDynamics.Coordinator 1 6 Info Configuration creating new coordinator configuration instance 2017-09-27 15:57:58.2994 163472 AppDynamics.Coordinator 1 6 Info MachineAgentManager #################################################################################### 2017-09-27 15:57:58.2994 163472 AppDynamics.Coordinator 1 6 Info MachineAgentManager Machine Agent started 2017-09-27 15:57:58.2994 163472 AppDynamics.Coordinator 1 6 Info MachineAgentManager Machine Agent version: 4.2.15.10 2017-09-27 15:57:58.4064 163472 AppDynamics.Coordinator 1 6 Info MachineAgentManager Started Agent Scheduler 2017-09-27 15:57:58.4064 163472 AppDynamics.Coordinator 1 6 Info MachineAgentManager Scheduling Machine Agent Registration .... 2017-09-27 15:57:58.4174 163472 AppDynamics.Coordinator 1 6 Info RegistrationChannel Reregistration Check is : [enabled]. 2017-09-27 15:57:58.4254 163472 AppDynamics.Coordinator 1 6 Info CoordinatorService coordinator service initialized successfully 2017-09-27 15:57:58.4254 163472 AppDynamics.Coordinator 1 6 Info CoordinatorService Starting communicator... 2017-09-27 15:57:58.4474 163472 AppDynamics.Coordinator 1 17 Info CoordinatorCommunicator starting named pipe server 2017-09-27 15:57:58.4564 163472 AppDynamics.Coordinator 1 24 Info RegistrationChannel using controller host [wm-appdynamics-qa-ctrl02]; controller port [8090] 2017-09-27 15:57:58.5154 163472 AppDynamics.Coordinator 1 31 Info LogFilePreparer zipping up agent logs to file: C:\Windows\TEMP\AppDynamicsLogs1777a634-e7da-4019-be1c-7b8c34b44170.zip 2017-09-27 15:57:58.5154 163472 AppDynamics.Coordinator 1 32 Info LogFilePreparer zipping up agent logs to file: C:\Windows\TEMP\AppDynamicsLogs8a1ee9b5-53ca-4bbc-b90a-f31cd4835a67.zip 2017-09-27 15:57:59.6896 163472 AppDynamics.Coordinator 1 24 Info RegistrationChannel setting unique host information Host Name [DDWAS6162] 2017-09-27 15:57:59.6896 163472 AppDynamics.Coordinator 1 24 Info RegistrationChannel setting agent version [4.2.15.10] 2017-09-27 15:57:59.6896 163472 AppDynamics.Coordinator 1 24 Info RegistrationChannel setting agent properties [] 2017-09-27 15:57:59.6896 163472 AppDynamics.Coordinator 1 24 Info RegistrationChannel setting agent install dir [C:\Program Files\AppDynamics\AppDynamics .NET Agent\\] 2017-09-27 15:57:59.6896 163472 AppDynamics.Coordinator 1 24 Info RegistrationChannel setting agent type [MACHINE_AGENT] 2017-09-27 15:57:59.6896 163472 AppDynamics.Coordinator 1 24 Info RegistrationChannel setting agent application(s) [EBCOther-QAPE, EBCReferenceData-QAPE, EBCClientFinancials-QAPE, EBC-CapitalMarketServices-QAPE, EBCClientDemographics-QAPE, EBC-Fainfo-QAPE, EBCAppInfrastructure-QAPE, EBCClientReportingServicing-QAPE, DIP-QAPE] 2017-09-27 15:57:59.6896 163472 AppDynamics.Coordinator 1 24 Info RegistrationChannel setting agent tier name [Machine Agent] 2017-09-27 15:57:59.6896 163472 AppDynamics.Coordinator 1 24 Info RegistrationChannel setting agent node name [DDWAS6162] 2017-09-27 15:57:59.6896 163472 AppDynamics.Coordinator 1 24 Info RegistrationChannel Sending Registration request 2017-09-27 15:57:59.7726 163472 AppDynamics.Coordinator 1 24 Info RegistrationChannel Auto agent registration attempted: Application Name [EBCOther-QAPE,EBCReferenceData-QAPE,EBCClientFinancials-QAPE,EBC-CapitalMarketServices-QAPE,EBCClientDemographics-QAPE,EBC-Fainfo-QAPE,EBCAppInfrastructure-QAPE,EBCClientReportingServicing-QAPE,DIP-QAPE] Component Name [Machine Agent] Node Name [DDWAS6162] 2017-09-27 15:57:59.7726 163472 AppDynamics.Coordinator 1 24 Info RegistrationChannel Auto agent registration SUCCEEDED! 2017-09-27 15:57:59.7726 163472 AppDynamics.Coordinator 1 24 Info MachineAgentManager Registered machine/collector agent with machine ID [809] 2017-09-27 15:57:59.7816 163472 AppDynamics.Coordinator 1 24 Info MachineAgentManager Starting Machine Agent .... 2017-09-27 15:57:59.7816 163472 AppDynamics.Coordinator 1 24 Info ControllerTimeSkewHandler Skew Handler is : [enabled]. 2017-09-27 15:57:59.8626 163472 AppDynamics.Coordinator 1 24 Info MachineAgentManager Metrics Metric Service is : [enabled]. 2017-09-27 15:57:59.9006 163472 AppDynamics.Coordinator 1 24 Info IISMetricManager Started IIS metric collection 2017-09-27 15:57:59.9006 163472 AppDynamics.Coordinator 1 24 Info MachineAgentManager Scheduling metric polling period of 60 with cache timeout of 1 2017-09-27 15:57:59.9226 163472 AppDynamics.Coordinator 1 24 Info MachineAgentManager starts EventLog listener 2017-09-27 15:57:59.9226 163472 AppDynamics.Coordinator 1 24 Info EventLogListener added EventLog for listening: [Application] 2017-09-27 15:57:59.9226 163472 AppDynamics.Coordinator 1 24 Info EventLogListener added EventLog for listening: [System] 2017-09-27 15:57:59.9226 163472 AppDynamics.Coordinator 1 24 Info EventLogListener added a new rule for monitoring .NET crash events: [Level = Warning, Source = Application Error] 2017-09-27 15:57:59.9366 163472 AppDynamics.Coordinator 1 24 Info EventLogListener added a new rule for monitoring .NET crash events: [Level = Warning, Source = .NET Runtime] 2017-09-27 15:57:59.9366 163472 AppDynamics.Coordinator 1 24 Info EventLogListener added a new rule for monitoring .NET crash events: [Level = Information, Source = Windows Error Reporting] 2017-09-27 15:57:59.9366 163472 AppDynamics.Coordinator 1 24 Info EventLogListener added a new rule for monitoring .NET crash events: [Level = Warning, Source = WAS] 2017-09-27 15:57:59.9366 163472 AppDynamics.Coordinator 1 24 Info EventLogListener starts listen EventLog: [Application] 2017-09-27 15:57:59.9366 163472 AppDynamics.Coordinator 1 24 Info EventLogListener starts listen EventLog: [System] 2017-09-27 15:57:59.9366 163472 AppDynamics.Coordinator 1 24 Info EventLogListener schedules to clean entries older than [60] sec every [60] sec 2017-09-27 15:57:59.9366 163472 AppDynamics.Coordinator 1 24 Info ProcessMonitor starts process monitoring for all running and future IIS processes and running executables (standalones and windows services) instrumented by the Agent 2017-09-27 15:58:01.3007 163472 AppDynamics.Coordinator 1 36 Error MachineAgentManager Metrics Maximum metrics limit reached [200] no new metrics can be created. This exception will not repeat until restart.Exception: com.appdynamics.ee.agent.commonservices.metricgeneration.metrics.spi.qe: Maximum metrics limit reached [200] no new metrics can be created. This exception will not repeat until restart."   DDWAS6162 in the log is one of the hosts that is missing   Do we need to increase the max number metrics & how?  Please advise if there could be any other reason   Thanks! Sundar ... View more