JBoss AS 7 plug-in for JBoss ON fails to discover server and logs error "Invalid port: 0" if non-HTTPS management interface is not defined

Solution Verified - Updated -

Issue

  • Invalid port: 0 error when agent is trying to discover JBoss Enterprise Application Platform (EAP) 6 on HTTPS management port.
  • JBoss EAP 6 management plug-in does not support a secure HTTP transport.
  • Agent is not able to discover JBoss EAP with the following error:
        ERROR [ResourceDiscoveryComponent.invoker.daemon-1] (rhq.modules.plugins.jbossas7.HostControllerDiscovery)- Discovery of a JBossAS7 Host Controller Resource failed for process: pid=[30641], name=[/etc/alternatives/java_sdk/bin/java], ppid=[30619].
        java.lang.IllegalArgumentException: Invalid port: 0
            at org.rhq.modules.plugins.jbossas7.ASConnection.<init>(ASConnection.java:82)
            at org.rhq.modules.plugins.jbossas7.BaseProcessDiscovery$ProductInfo.getFromRemote(BaseProcessDiscovery.java:603)
            at org.rhq.modules.plugins.jbossas7.BaseProcessDiscovery.buildResourceDetails(BaseProcessDiscovery.java:212)
            at org.rhq.modules.plugins.jbossas7.BaseProcessDiscovery.discoverResources(BaseProcessDiscovery.java:136)
            at sun.reflect.GeneratedMethodAccessor26.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.util.DiscoveryComponentProxyFactory$ComponentInvocationThread.call(DiscoveryComponentProxyFactory.java:293)
            at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
            at java.util.concurrent.FutureTask.run(FutureTask.java:166)
            at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
            at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
            at java.lang.Thread.run(Thread.java:636)
  • Discovery of JBoss EAP fails when management interface is using SSL.
  • Unable to discovery JBoss application server using secure management interface
  • Is there anyway to discover EAP6 instances via JON without enabling the HTTP management interface ?
  • JBoss is configured so the management interface can only be accessed using the https-interface. When we made this change, this prevented JON from connecting to the JBoss instance and managing it. We are unable to authenticate using https-interface.

Environment

  • Red Hat JBoss Operations Network (ON)
    • 3.1.1
    • 3.1.2
    • 3.2.0
    • 3.3.0
  • Red Hat JBoss Enterprise Application Platform (EAP) 6 management plug-in for JBoss ON

  • Management interface for JBoss application server is configured only for HTTPS or SSL:

    • Standalone:

      ...
<management-interfaces>
    ...
    <http-interface security-realm="ManagementRealm">
        <socket-binding https="management-https"/>
    </http-interface>
</management-interfaces>
...

    • Domain:

      ...
<management-interfaces>
    ...
    <http-interface security-realm="ManagementRealm">
        <socket interface="management" secure-port="${jboss.management.https.port:9943}" />
    </http-interface>
</management-interfaces>
...

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

New to Red Hat?

Learn more about Red Hat subscriptions

Close

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