[
https://issues.jboss.org/browse/AS7-5109?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry commented on AS7-5109:
---------------------------------------
This is a documentation issue in the EAP docs, and should be moved to Bugzilla, since
that's where the EAP docs team is tracking stuff.
To bind the management sockets to 192.168.193.139 use:
./domain.sh -bmanagement=192.168.193.139
See "Controlling the Bind Address with -b" in the AS 7.1 community docs at
https://docs.jboss.org/author/display/AS71/Command+line+parameters for details as to why
that is.
When starting JBoss AS -b should work no matter how I start JBoss AS
to bind it to the local interface
------------------------------------------------------------------------------------------------------
Key: AS7-5109
URL:
https://issues.jboss.org/browse/AS7-5109
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management
Affects Versions: 7.1.2.Final (EAP)
Reporter: Jim Tyrrell
Assignee: Brian Stansberry
Labels: eap6-req
When starting JBoss as with the following command:
./domain.sh -b 192.168.193.139 -Djboss.domain.base.dir=/home/jimtyrrell/Servers/machine1/
--host-config=host-master.xml
It does not bind to the passed in IP Address. Instead it binds to localhost 127.0.0.1.
It should have bound to 192.168.192.139 in this instance.
Instead I had to pass in the parameter like this:
./domain.sh -Djboss.domain.base-dir=/home/jimtyrrell/Servers/machine1/
--host-config=host-master.xml -Djboss.bind.address.management=192.168.193.139
Please expand this ticket to any and all shipped configuration starting files so that the
host binding works per the help info via a -b binding.
--
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