AppD Archive

ActiveMQ Monitoring Extension Problem: NoClassDefFoundError - FileAlterationListener

CommunityUser
Splunk Employee
Splunk Employee

Team, 

I have installed activemq monitoring extension under Machine Server Agent in standalone machine. When I start machine server agent, i got below exception.

I have seen the same exception discussed over this forum for RabbitMQ. Hence I tried updating classpath with commons-httpclient-3.1.jar in monitors/ActiveMQMonitor/monitor.xml. Still getting this same below execption. 

Can you please help me to setup this?

[Worker-1] 19 Dec 2016 13:23:33,357 INFO ProcessMonitor - Finished collecting metrics...
[Worker-1] 19 Dec 2016 13:23:33,359 INFO ProcessMonitor - Finished printing metrics...
[Worker-1] 19 Dec 2016 13:23:33,359 INFO ProcessMonitor - New round of metric collection started
[Agent-Scheduler-1] 19 Dec 2016 13:23:35,676 ERROR PeriodicTaskRunner - Error creating environment task
java.lang.NoClassDefFoundError: org/apache/commons/io/monitor/FileAlterationListener
at com.appdynamics.extensions.activemq.ActiveMQMonitor.initialize(ActiveMQMonitor.java:83)
at com.appdynamics.extensions.activemq.ActiveMQMonitor.execute(ActiveMQMonitor.java:65)
at com.singularity.ee.agent.systemagent.components.monitormanager.managed.MonitorTaskRunner.runTask(MonitorTaskRunner.java:143)
at com.singularity.ee.agent.systemagent.components.monitormanager.managed.PeriodicTaskRunner.runTask(PeriodicTaskRunner.java:95)
at com.singularity.ee.agent.systemagent.components.monitormanager.managed.PeriodicTaskRunner.run(PeriodicTaskRunner.java:48)
at com.singularity.ee.util.javaspecific.scheduler.AgentScheduledExecutorServiceImpl$1.run(AgentScheduledExecutorServiceImpl.java:34)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at com.singularity.ee.util.javaspecific.scheduler.ADFutureTask$Sync.innerRunAndReset(ADFutureTask.java:290)
at com.singularity.ee.util.javaspecific.scheduler.ADFutureTask.runAndReset(ADFutureTask.java:145)
at com.singularity.ee.util.javaspecific.scheduler.ADScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ADScheduledThreadPoolExecutor.java:82)
at com.singularity.ee.util.javaspecific.scheduler.ADScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ADScheduledThreadPoolExecutor.java:160)
at com.singularity.ee.util.javaspecific.scheduler.ADScheduledThreadPoolExecutor$ScheduledFutureTask.run(ADScheduledThreadPoolExecutor.java:184)
at com.singularity.ee.util.javaspecific.scheduler.ADThreadPoolExecutor$Worker.runTask(ADThreadPoolExecutor.java:667)
at com.singularity.ee.util.javaspecific.scheduler.ADThreadPoolExecutor$Worker.run(ADThreadPoolExecutor.java:692)
at java.lang.Thread.run(Thread.java:724)
Caused by: java.lang.ClassNotFoundException: org.apache.commons.io.monitor.FileAlterationListener
at com.singularity.ee.util.loader.FileSystemClassLoader.findClass(FileSystemClassLoader.java:322)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at com.singularity.ee.util.loader.FileSystemClassLoader.loadClass(FileSystemClassLoader.java:274)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
... 15 more

My ActiveMQ config.yml:

root@XX : XX@XX # head -20 monitors/ActiveMQMonitor/config.yml
### ANY CHANGES TO THIS FILE DOES NOT REQUIRE A RESTART ###

#This will create this metric in all the tiers, under this path
metricPrefix: Custom Metrics|ActiveMQ

#This will create it in specific Tier. Replace <TIER_NAME>
#metricPrefix: Server|Component:<TIER_NAME>|Custom Metrics|ActiveMQ

# List of ActiveMQ Servers
servers:
- host: "localhost"
port: 8161
username: "<<user name to access activemq console>>"
password: "<<password to access activemq console>>"
#displayName is a required field. This will be your server name that will show up in metric path.
displayName: "activemqb"


# number of concurrent tasks.
# This doesn't need to be changed unless many servers are configured

0 Karma
Get Updates on the Splunk Community!

App Platform's 2025 Year in Review: A Year of Innovation, Growth, and Community

As we step into 2026, it’s the perfect moment to reflect on what an extraordinary year 2025 was for the Splunk ...

Operationalizing Entity Risk Score with Enterprise Security 8.3+

Overview Enterprise Security 8.3 introduces a powerful new feature called “Entity Risk Scoring” (ERS) for ...

Unlock Database Monitoring with Splunk Observability Cloud

  In today’s fast-paced digital landscape, even minor database slowdowns can disrupt user experiences and ...