Red Hat Bugzilla – Bug 754858
as7: discovery fails with newer versions of as7.1
Last modified: 2015-11-01 19:42:13 EST
THis bug is to further work on the issue on top of the commits cited at the bottom.
+++ This bug was initially created as a clone of Bug #754838 +++
As7.1 has changed the setup of the management port to now also use a socket-binding reference.
The current code is not able to discover that versions and fails with an exception.
Stop-gap fix is to assume a default port if no other port is given in the
<socket-binding name="management-http" interface="management" port="9990"/>
older versions and eap6a2 ( dr5: )
<native-interface interface="management" port="9999"/>
<http-interface interface="management" port="9990"/>
--- Additional comment from firstname.lastname@example.org on 2011-11-17 16:37:04 EST ---
In addition the hostname is also not correctly determined.
--- Additional comment from email@example.com on 2011-11-17 17:24:16 EST ---
aad83e7 in release branch
f2edb384f3 in master
check for empty port and/or host and use default values in that case.
19097edb5d591dae5ae6fdf7565b682cd5b1506c in master
EAP6 DR8 is discovered fine both Standalone and DomainController
changing status of VERIFIED BZs for JON 2.4.2 and JON 3.0 to CLOSED/CURRENTRELEASE