TIBCO EMS 8.2 support with Json configuration

[CommunityUser]

Hi Team, 

I tried configuring appdynamics-3.7.21 with TIBCO EMS server 8.2 whihc is using Json configuration files instead of .conf files.

I have followed steps provided in learn section i.e http://community.appdynamics.com/t5/eXchange-Community-AppDynamics/TibcoEMS-Monitoring-Extension/idi... .

I see below error in logs after setup.

Error log:

Response Object :<response>
<response-code>1</response-code>
<execution-output>System agent [180] not associated with application, metric registration request refused.</execution-output>
</response>
at com.singularity.ee.agent.commonservices.metricgeneration.AMetricSubscriber.registerMetrics(AMetricSubscriber.java:209)
at com.singularity.ee.agent.commonservices.metricgeneration.MetricGenerationService.registerMetrics(MetricGenerationService.java:264)
at com.singularity.ee.agent.commonservices.metricgeneration.MetricReporter.run(MetricReporter.java:91)
at com.singularity.ee.util.javaspecific.scheduler.AgentScheduledExecutorServiceImpl$SafeRunnable.run(AgentScheduledExecutorServiceImpl.java:102)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at com.singularity.ee.util.javaspecific.scheduler.ADFutureTask$Sync.innerRunAndReset(ADFutureTask.java:315)
at com.singularity.ee.util.javaspecific.scheduler.ADFutureTask.runAndReset(ADFutureTask.java:150)
at com.singularity.ee.util.javaspecific.scheduler.ADScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ADScheduledThreadPoolExecutor.java:138)
at com.singularity.ee.util.javaspecific.scheduler.ADScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ADScheduledThreadPoolExecutor.java:223)
at com.singularity.ee.util.javaspecific.scheduler.ADScheduledThreadPoolExecutor$ScheduledFutureTask.run(ADScheduledThreadPoolExecutor.java:253)
at com.singularity.ee.util.javaspecific.scheduler.ADThreadPoolExecutor$Worker.runTask(ADThreadPoolExecutor.java:683)
at com.singularity.ee.util.javaspecific.scheduler.ADThreadPoolExecutor$Worker.run(ADThreadPoolExecutor.java:715)
at java.lang.Thread.run(Thread.java:662)
[AD Thread-Metric Reporter0] 08 Jan 2015 20:31:14,267 ERROR ManagedMonitorDelegate - Error registering metrics
com.singularity.ee.agent.commonservices.metricgeneration.metrics.MetricRegistrationException: Error registering metrics with controller. Response:<response>
<response-code>1</response-code>
<execution-output>System agent [180] not associated with application, metric registration request refused.</execution-output>
</response>
at com.singularity.ee.agent.commonservices.metricgeneration.AMetricSubscriber.registerMetrics(AMetricSubscriber.java:272)
at com.singularity.ee.agent.commonservices.metricgeneration.MetricGenerationService.registerMetrics(MetricGenerationService.java:264)
at com.singularity.ee.agent.commonservices.metricgeneration.MetricReporter.run(MetricReporter.java:91)
at com.singularity.ee.util.javaspecific.scheduler.AgentScheduledExecutorServiceImpl$SafeRunnable.run(AgentScheduledExecutorServiceImpl.java:102)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at com.singularity.ee.util.javaspecific.scheduler.ADFutureTask$Sync.innerRunAndReset(ADFutureTask.java:315)
at com.singularity.ee.util.javaspecific.scheduler.ADFutureTask.runAndReset(ADFutureTask.java:150)
at com.singularity.ee.util.javaspecific.scheduler.ADScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ADScheduledThreadPoolExecutor.java:138)
at com.singularity.ee.util.javaspecific.scheduler.ADScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ADScheduledThreadPoolExecutor.java:223)
at com.singularity.ee.util.javaspecific.scheduler.ADScheduledThreadPoolExecutor$ScheduledFutureTask.run(ADScheduledThreadPoolExecutor.java:253)
at com.singularity.ee.util.javaspecific.scheduler.ADThreadPoolExecutor$Worker.runTask(ADThreadPoolExecutor.java:683)
at com.singularity.ee.util.javaspecific.scheduler.ADThreadPoolExecutor$Worker.run(ADThreadPoolExecutor.java:715)
at java.lang.Thread.run(Thread.java:662)
Caused by: com.singularity.ee.agent.commonservices.metricgeneration.metrics.MetricRegistrationException: Invalid metric registration response from controller, empty map returned. Metrics sent for registration

Regards,

Shiva

[Arun_Dasetty]

Hi Shiva,

We earlier see such errors "System agent [180] not associated with application, metric registration request refused", When machine is trying to either result in duplicate node name registration Or trying to register without application-name, tier-name, node-name Or -Dappdynamics.agent.uniqueHostId JVM arg as suggested in below docs

- https://docs.appdynamics.com/display/PRO40/Configure+Multiple+Standalone+Machine+Agents+for+One+Mach... 

If you are trying to do auto machine agent registration without providing app,tier and node-name details, please be sure the scenarion works only there are no multiple appserver agent nodes associated to different application-name from same machine agent instance to the controller.

Can you please provide archive of <machineagent_dir>/logs path and also screenshot with application name(application to which in UI you want to associate) filtered under Settings -> AppDynamics Agents section from controller UI to debug further, if configuring machine agent as per above doc link does not help post machine agent restart. 

Keep us posted how it goes.

Regards,

Arun

[Arun_Dasetty]

Hi Shiva,

Have the provided suggestions and doc link helped, if not please send the details requested to debug further.

Regards,

Arun