Looks like that was fixed a day ago:
https://github.com/jbossas/jboss-as/commit/ea7b9560b5358a1689439099680e49...
On 3/24/11 5:58 PM, Scott Stark wrote:
I'm using standalone.sh, and definitely see that I can access the
8080
port using any incoming address. Now netstat is showing everything but
8080 on 127.0.0.1:
[335](ironmaiden:IRONJACAMAR_1_0_0_BETA4)> netstat -an
Active Internet connections (including servers)
Proto Recv-Q Send-Q Local Address Foreign Address (state)
[103](ironmaiden:bin)> netstat -an | grep LISTEN
tcp4 0 0 127.0.0.1.5445 *.* LISTEN
tcp4 0 0 127.0.0.1.5455 *.* LISTEN
tcp46 0 0 *.8080 *.* LISTEN
tcp4 0 0 127.0.0.1.4712 *.* LISTEN
tcp4 0 0 127.0.0.1.4714 *.* LISTEN
tcp4 0 0 127.0.0.1.1091 *.* LISTEN
tcp4 0 0 127.0.0.1.9990 *.* LISTEN
tcp4 0 0 127.0.0.1.1090 *.* LISTEN
tcp4 0 0 127.0.0.1.9999 *.* LISTEN
tcp4 0 0 127.0.0.1.56537 *.* LISTEN
[99](ironmaiden:bin)> telnet 192.168.1.106 8080
Trying 192.168.1.106...
Connected to 192.168.1.106.
Escape character is '^]'.
^]
telnet> quit
Connection closed.
[100](ironmaiden:bin)> telnet localhost 8080
Trying ::1...
Connected to localhost.
Escape character is '^]'.
^]
telnet> q
Connection closed.
[101](ironmaiden:bin)>
On 3/24/11 2:21 PM, Brian Stansberry wrote:
> Quick double check: are you using standalone.sh or domain.sh?
>
> Your snippet below is from standalone.xml. I just tried standalone.sh
> and all sockets were bound to 127.0.0.1. But domain.xml has a different
> config; it uses interface "external" which is configured for
> <any-ipv4-address/>.
>
>
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat