IP binding in WF 8.1.0

[kawa.wolf]

Hi everybody

I have a problem in ip binding. I have an application on a server, and when using "localhost:prot" in the browser inside server, it is ok, so I am sure the problem is not from my application, but from configuration of the server.

I set the wildfly-8.1.0.Final\standalone\configuration\standalone.xml like this:

    <interfaces>

        <interface name="management">

            <inet-address value="${jboss.bind.address.management:MyValidIp}"/>

        </interface>

        <interface name="public">

            <inet-address value="${jboss.bind.address:MyValidIp}"/>

        </interface>

        <interface name="unsecure">

            <inet-address value="${jboss.bind.address.unsecure:MyValidIp}"/>

        </interface>

    </interfaces>

But I am not able to connect my application via "MyValidIp" address, and I see no service listening on this port of "MyValidIp" when I use cmd/netstat -na. Any idea will be appreciated.

Thanks for reading.

[wdfink]

If you replace "MyValidIp" with localhost it works?

Did you checked the logfile to see which IP is used for binding, by default it show for http (8080) which ip/port is used

[vipinlal.tg]

    <interfaces>
        <interface name="management">
            <inet-address value="${jboss.bind.address.management:127.0.0.1}"/>
        </interface>
        <interface name="public">
            <any-address/>
        </interface>
        <interface name="unsecure">
            <inet-address value="${jboss.bind.address.unsecure:127.0.0.1}"/>
        </interface>
    </interfaces>

use this script

[datasae]

I would like to know how to get an application on wildfly outside the server example

200.159.25.63:8080/nomeaplicativo or a DDNS

servidor.ddns.com.br:8080:nomeaPLICATIVO

because I have the need to install wildfly and to deploy my application and then call the application from anywhere

[kawa.wolf]

Hi everybody. Vipinlal and Wolf, thank you for your responses.

I figured out the problem and solved it. So I write the solution, and I hope it can help others, specially Eduardo Melo Andrade.

I tried Vipinlal T answer, but it didn't worked. Then, I defined a new interface, say "someInterface" , defined it with "any ip v 4", and then added this to the standalone-full.xml in the WF server:

<socket-binding-group name="standard-sockets" default-interface="someInterface”>

I guess default-interface property is the key. By default, it is "public" interface.

Hope it could help other.