EAP Host Controller in JBoss ON is marked as down due to agent unable to detect HostController's process-type

Solution Verified - Updated -

Issue

  • JBoss ON shows EAP Host Controller as down even it is up and running
  • The agent.log file shows:

    ... WARN  [ResourceContainer.invoker.daemon-5] (rhq.modules.plugins.jbossas7.HostControllerComponent)- Unable to detect HostController's process-type
    java.util.concurrent.TimeoutException: Read attribute operation timed out
            at org.rhq.modules.plugins.jbossas7.BaseComponent.readAttribute(BaseComponent.java:873)
            ...
    
  • Agent is able to connect only with domain but not with host controller;

  • Host Controller marked as DOWN even though it has been UP;
  • The agent.log file contains:

    ... WARN  [ResourceContainer.invoker.daemon-5] (rhq.modules.plugins.jbossas7.HostControllerComponent)- Unable to detect HostController's process-type
    java.lang.Exception: Failed to read attribute [process-type] of address [] - response: Result{outcome='failure', failureDescription=The server closed the connection before sending the response, rolled-back=false, rolledBack=false}
            at org.rhq.modules.plugins.jbossas7.BaseComponent.readAttribute(BaseComponent.java:885)
            ...
    

Environment

  • Red Hat JBoss Operations Network (ON) 3.3
  • Red Hat Enterprise Application Platform (EAP) 6.4.7
  • EAP started in domain mode;

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
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.