Fuse or ActiveMQ resource discovery reports "Failed to extract JMX service URL for process with PID [...]" due to failure in getProcCredName

Solution Unverified - Updated -

Issue

  • Agent is not detecting or discovering ActiveMQ
  • agent.log contains discovery warning:

    WARN  [ResourceDiscoveryComponent.invoker.daemon-2] (org.jbosson.plugins.fuse.JBossFuseContainerDiscoveryComponent)- Error when trying to discover Fuse Server process [ProcessScanResult: scan=[ProcessScan: query=[process|basename|match=^java.*,arg|-Dkaraf.home|match=.*,arg|-Dkaraf.base|match=.*,arg|*|match=org\.apache\.karaf\.(main|shell\.wrapper)\.Main], name=[null]], info=[process: pid=[1234], name=[java], ppid=[123]]] (enable DEBUG for stack trace): java.lang.RuntimeException: Failed to extract JMX service URL for process with PID [1234].
    
  • Agent's debug log shows following discovery failure:

    java.lang.RuntimeException: Failed to extract JMX service URL for process with PID [1234].
        at org.rhq.plugins.jmx.util.JvmUtility.extractJMXServiceURL(JvmUtility.java:100)
    Caused by: java.lang.NullPointerException
        at org.rhq.plugins.jmx.util.JvmUtility.attachToVirtualMachine(JvmUtility.java:117)
    
  • Unable to discover JBoss Fuse Container, ActiveMQ Server, Fabric Container, or Servicemix4

Environment

  • Red Hat JBoss Operations Network (ON)
    • 3.3.0
    • 3.3.1
    • 3.3.2
    • 3.3.3
    • 3.3.4
    • 3.3.5
    • 3.3.6
    • 3.3.7
    • 3.3.8
    • 3.3.9
  • Red Hat JBoss Fuse or A-MQ/AMQ
    • JBoss A-MQ 6.2.1
    • JBoss Fuse 6.2.1
  • Linux or UNIX based operating system
  • JBoss ON agent's native support has not been disabled
  • JBoss ON agent has access to Java JDK/SDK which includes the Java Attach API libraries
  • The JBoss ON agent is not running as root

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