[
https://issues.jboss.org/browse/AS7-3974?page=com.atlassian.jira.plugin.s...
]
Paul Ferraro edited comment on AS7-3974 at 2/29/12 12:41 PM:
-------------------------------------------------------------
To clarify, this is a request to support any loopback address via the -b argument, without
requiring the user to modify the <interfaces/> configuration changing
<inet-address value="${jboss.bind.address:127.0.0.1}"/> to
<loopback-address value="${jboss.bind.address:127.0.0.1}"/>.
was (Author: pferraro):
To clarify, this is a request to support any loopback addresses via the -b argument,
without requiring the user to modify the <interfaces/> configuration changing
<inet-address value="${jboss.bind.address:127.0.0.1}"/> to
<loopback-address value="${jboss.bind.address:127.0.0.1}"/>.
Loopback addresses in the range 127.0.0.2 - 127.255.255.255 should be
supported
-------------------------------------------------------------------------------
Key: AS7-3974
URL:
https://issues.jboss.org/browse/AS7-3974
Project: Application Server 7
Issue Type: Feature Request
Affects Versions: 7.1.0.Final
Environment: Linux Fedora 13
Reporter: Bela Ban
When starting JBoss like this: "standalone.sh -b 127.0.0.2 -c
standalone-ha.xml", the startup fails because 127.0.0.2 cannot be resolved.
However, a loopback address should be recognized even if it doesn't resolve to an
interface. The code below works for example:
{code}
InetAddress addr=InetAddress.getByName("127.0.0.5");
boolean is_loopback=addr.isLoopback(); // should be true
{code}
Loopback addresses are very useful for local testing, ie. starting of multiple JBoss
instances on the same box.
--
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