Hide Forgot
Description of problem: The JBoss AS resources (for both AS4 and AS5 plugins) are named after the binding address and JNP port. I.e. by default they are called 0.0.0.0:1099 which is both nearly meaningless and ugly. How reproducible: always Steps to Reproduce: 1. start a jboss as 2. let it be discovered by an agent 3. observe the autodiscovery queue in the RHQ server UI. Actual results: A JBoss AS resource is called something like 0.0.0.0:1099. Expected results: Something more meaningful. Ideally the name of the "significant" application deployed on the server or at least the same info as in previous versions of RHQ. I.e. hostname:jnpPort
Commit bb5e7a9 (in bugfixes branch) implements the second option, i.e.: hostname:jnpPort I'm leaving this bug open though to track the need to come up with something more clever.
We can raise a new issue if there are better suggestions
So, I have three EAP5 instances running on a server, using different loopback ip addresss (127.0.0.1, 127.0.0.2, 127.0.0.3) In the JON UI they appear (in alphanumeric order) as: 127.0.0.2:1099 127.0.0.3:1099 localhost.localdomain:1099 Is this what we are expecting?
that seems ok... the 127.0.0.1 is resolved to a hostname because it probably has an entry in your /etc/hosts unlike the rest of the loopbacks you used. Because you explicitly specified the binding addresses using the -b option, those binding addresses is what you see in the resource names. If you didn't specify the -b option (or explicitly set it to "0.0.0.0", i.e. all interfaces), the server would get the hostname of the machine it runs on (as reported by the system).
QA Verified.
Mass-closure of verified bugs against JON.