[
https://issues.jboss.org/browse/AS7-1476?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry updated AS7-1476:
----------------------------------
Fix Version/s: 7.1.0.CR1
For a standalone server, the management interfaces should take a socket-binding reference
like anything else.
For a Host Controller, using expressions to change the port is the way to go. An HC has no
socket-binding-group.
management-interfaces ports don't tie into the
socket-binding-group/port-offset
-------------------------------------------------------------------------------
Key: AS7-1476
URL:
https://issues.jboss.org/browse/AS7-1476
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management
Affects Versions: 7.0.0.Final
Reporter: Scott Stark
Assignee: Scott Stark
Fix For: 7.1.0.CR1
If isolation of jboss instances is being done via port offsets using the port-offset
attribute on the socket-binding-group, one still has to separately update the ports in the
management-interfaces:
<management-interfaces>
<native-interface interface="management"
port="9999"/>
<http-interface interface="management"
port="9990"/>
</management-interfaces>
I'm not sure why this cannot be configured as any other port. At a minimum, the
management-interfaces element should also have a port-offset attribute.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira