JBoss ON agent unable to monitor JBoss Fuse server if only guava version 18 library exists

Solution Unverified - Updated -

Issue

  • JBoss Fuse server down;
  • Agent.log file contains the following error:

    ... DEBUG [InventoryManager.discovery-1] (rhq.core.pc.util.DiscoveryComponentProxyFactory)- Call to [org.jbosson.plugins.fuse.JBossFuseContainerDiscoveryComponent.getAdditionalClasspathUrls()] with args [[org.rhq.core.pluginapi.inventory.ResourceDiscoveryContext@45ebab7e, key=JBoss Fuse Container{/path/to/fuse/fabric8-karaf-1.2.0.redhat-630310},name=JBoss Fuse Container [fuse1]{/path/to/fuse/fabric8-karaf-1.2.0.redhat-630310} JBoss Fuse Container [fuse1],type=JBoss Fuse Container,version=1.2.0.redhat-630310,description=JBoss Fuse Container Process, monitored via JMX Remoting]] failed.
    java.util.concurrent.ExecutionException: java.lang.Exception: Discovery component invocation failed.
    ...
    Caused by: org.rhq.core.pluginapi.inventory.InvalidPluginConfigurationException: Missing Google Guava library guava-*.jar in /path/to/fuse/fabric8-karaf-1.2.0.redhat-630310/system
    

Environment

  • Red Hat JBoss Operations Network (ON) 3.3.8
  • Red Hat JBoss Fuse (Fuse) 6.3.0
  • Fuse system folder contains only guava library version 18.0.0.redhat-1:

    $ cd $FUSE_HOME/system/com/google/guava/guava
    $ ls -l
    $ drwxrwxr-x. 2 fuseusr fuseusr 4096 Jan  9 11:30 18.0.0.redhat-1
    

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In