Standalone ActiveMQ 5.8 can not be auto-discovered by JON

Solution Verified - Updated -


When trying to monitor the standalone version of ActiveMQ 5.8, the auto-discovery component is not working. Digging into the kogs we can see the following message:

2013-06-17 21:18:39,891 WARN [ResourceDiscoveryComponent.invoker.daemon-2] (org.jbosson.plugins.fuse.FuseServerDiscoveryComponent)- Error when trying to discover Fuse Server process [ProcessScanResult: scan=[ProcessScan: query=[process|basename|match=^java.*,arg|-Dactivemq.home|match=.*], name=[null]], info=[process: pid=[3484], name=[/System/Library/Frameworks/JavaVM.framework/Home/bin/java], ppid=[3463]]] (enable DEBUG for stack trace): org.rhq.core.pluginapi.inventory.InvalidPluginConfigurationException: Version file activemq-all-([0-9\.\-(fuse)]*)\.jar could not be found in /Users/sjavurek/Fuse/JBossFuse/jboss-a-mq-6.0.0.redhat-015/extras/apache-activemq-5.8.0.redhat-60015


  • Fuse Message Broker 5.8
  • JBoss Operational Network 3.1.2

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content