JBoss ON agent log contains "EMS bean was null for Resource" message when target resource is no longer deployed

Solution Verified - Updated -

Issue

  • rhq-agent log throwing error EMS bean was null for Resource
  • How to resolve below errors that appear in agent.log:

    ERROR [InventoryManager.discovery-1] (rhq.core.pc.inventory.InventoryManager)- Failed to start component for Resource[id=10539, uuid=00d94249-8de2-7301-ac7b-f2495ed33b1d, type={JBossESB5}Actions, key=getInfo , name=getInfo , parent=MyESBService Service, version=5.2.0.GA] from synchronized merge.
    org.rhq.core.clientapi.agent.PluginContainerException: Failed to start component for resource Resource[id=10539, uuid=00d94249-8de2-7301-ac7b-f2495ed33b1d, type={JBossESB5}Actions, key=getInfo , name=getInfo , parent=MyESBService Service, version=5.2.0.GA].
        at org.rhq.core.pc.inventory.InventoryManager.activateResource(InventoryManager.java:1753)
        at org.rhq.core.pc.inventory.InventoryManager.refreshResourceComponentState(InventoryManager.java:3012)
        at org.rhq.core.pc.inventory.InventoryManager.processSyncInfo(InventoryManager.java:2757)
        at org.rhq.core.pc.inventory.InventoryManager.processSyncInfo(InventoryManager.java:2763)
        at org.rhq.core.pc.inventory.InventoryManager.processSyncInfo(InventoryManager.java:2763)
        at org.rhq.core.pc.inventory.InventoryManager.processSyncInfo(InventoryManager.java:2763)
        at org.rhq.core.pc.inventory.InventoryManager.processSyncInfo(InventoryManager.java:2763)
        at org.rhq.core.pc.inventory.InventoryManager.processSyncInfo(InventoryManager.java:2763)
        at org.rhq.core.pc.inventory.InventoryManager.synchInventory(InventoryManager.java:1105)
        at org.rhq.core.pc.inventory.InventoryManager.handleReport(InventoryManager.java:1079)
        at org.rhq.core.pc.inventory.AutoDiscoveryExecutor.call(AutoDiscoveryExecutor.java:129)
        at org.rhq.core.pc.inventory.AutoDiscoveryExecutor.run(AutoDiscoveryExecutor.java:91)
        ...
    Caused by: java.lang.IllegalStateException: EMS bean was null for Resource with type [{JBossESB5}Services] and key [jboss.esb:category=MessageCounter,deployment=mybus.esb,service-category=ReportManagement,service-name=MyESBService].
        at org.rhq.plugins.jmx.MBeanResourceComponent.getEmsBean(MBeanResourceComponent.java:139)
        at org.jbosson.plugins.jbossesb.ActionComponent.start(ActionComponent.java:94)
        at sun.reflect.GeneratedMethodAccessor34.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:616)
        at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:634)
        at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
        at java.util.concurrent.FutureTask.run(FutureTask.java:166)
        ... 3 more
    
  • JBoss ESB resource or one of its children reported as unavailable

Environment

  • Red Hat JBoss Operations Network (ON)
    • 3
  • Red Hat JBoss Enterprise SOA Platform
    • 5.1.0
    • 5.2.0
    • 5.3.0
  • JBoss ESB 5 plug-in for JBoss ON 3.1.2
  • JBoss ESB service in JBoss ON inventory
    • The ESB service has been redeployed since it was originally discovered by ON after one of its child components had been removed (services, actions, etc)

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