Camel-context resources are down in JBoss ON UI

Solution Unverified - Updated -


  • Camel context resource stopped using camel:context-stop is unavailable in JBoss ON UI;
  • Camel context resource is down and the following message is logged in the agent.log file:

    ... DEBUG [ResourceContainer.invoker.availCheck.daemon-1] (org.rhq.plugins.jmx.MBeanResourceComponent)- Avail check failed, MBean not available java.lang.IllegalStateException: EMS bean was null for Resource with type [ResourceType[id=0, name=CXF Endpoint, plugin=CXF, category=Service]] and key [,,port="myPort",service="{}myPort",type=Bus.Service.Endpoint].
        at org.rhq.plugins.jmx.MBeanResourceComponent.getEmsBean(
        at org.rhq.plugins.jmx.MBeanResourceComponent.isMBeanAvailable(
        at org.rhq.plugins.jmx.MBeanResourceComponent.getAvailability(
        at java.util.concurrent.ThreadPoolExecutor.runWorker(
        at java.util.concurrent.ThreadPoolExecutor$


  • Red Hat JBoss Operations Network (ON) 3.3
  • Red Hat JBoss Fuse (Fuse) 6
  • Camel context resources discovered by JBoss ON and then stopped.

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