JBAS015810: failed to resolve interface public

[mpfontana]

Hi, im trying to set up JBOSS 7AS to the interface 127.0.2.1, but just modifying the file standalone.xml on the following line, thats not working.

1. <interfaces> 
2.         <interface name="management"> 
3.             <inet-address value="${jboss.bind.address.management:127.0.0.1}"/> 
4.         </interface> 
5.         <interface name="public"> 
6.             <inet-address value="${jboss.bind.address:127.0.2.1}"/>
7.         </interface> 
8.         <interface name="unsecure"> 
9.             <inet-address value="${jboss.bind.address.unsecure:127.0.0.1}"/> 
10.         </interface> 
11.     </interfaces>

Im getting the following StackTrace:

• 15:58:12,484 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC00001: Failed to start service jboss.network.public: org.jboss.msc.service.StartException in service jboss.network.public: JBAS015810: failed to resolve interface public 

•     at org.jboss.as.server.services.net.NetworkInterfaceService.start(NetworkInterfaceService.java:97) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final] 

•     at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] 

•     at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] 

•     at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_38] 

•     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_38] 

•     at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_38] 

•  

• 15:58:15,898 INFO  [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report 

• JBAS014777:   Services which failed to start:      service jboss.network.public: org.jboss.msc.service.StartException in service jboss.network.public: JBAS015810: failed to resolve interface public 

For what i read, i need to map the ip, but i dont know how to do it. Can someone help me?

[nickarls]

Does the interface 127.0.2.1 work (tried pinging it)?

Does the AS start with standalone.(sh|bat) -b 127.0.2.1?

The "failed to resolve" sounds a bit strange.

[mpfontana]

No, thats not respond because its don't exist. I'm trying to set up a project, but i already have a service on the interface localhost and i need to change the interface when the Jboss is started. Why this jboss need to have a valid ip?

[nickarls]

We are talking physical network interfaces here, you can't just make them up, methinks.

[dlofthouse]

+1 you can not just make up these addresses - JBoss uses this to create the server sockets but if the address does not exist then there is nothing to listen on for incomming connection.

Why this jboss need to have a valid ip?

An alternative question is what use to you is an AS installation that you can not connect to due to not having a valid IP address?

What OS are you using?  You are reaching operating specific configuration here.

[mpfontana]

I don't know how Jboss 7 AS works, but in the previous version i was abble to set up an service in an ip on the network that does not exist. I use windows 8 x64 and use only academically.

[buuhsmead]

It seems to be a bug in jboss 7 which is going to be fixed in 7.1.3.....

So I created an additonal loopback entry in /etc/sysconfig/network-scripts/ifcfg-lo:1. And changed the content to:

DEVICE=lo:1

IPADDR=127.0.10.1

NETMASK=255.0.0.0

NETWORK=127.0.0.0

# If you're having problems with gated making 127.0.0.0/8 a martian,

# you can change this to something else (255.255.255.255, for example)

BROADCAST=127.255.255.255

ONBOOT=yes

NAME=loopback-1

And now I can use : ./standalone.sh -b 127.0.10.1

[tlarevo]

This reply might be too late, but for those who come looking for an answer heres my experience

This kind of error could occur if you happen to have specified bind address for JAVA_OPTS in your configs in standalone.conf

-Djboss.bind.address=192.168.xxx.xxx -Djboss.bind.address.management=192.168.xxx.xxx -Djboss.bind.address.unsecure=192.168.xxx.xxx

If so make sure you have given the correct IP for the bind address otherwise you'd see something similar to the above mentioned error. Of course there could be other reasons this is my experience.

[silean1]

Since this is the first what I've got from searching thru google, I will give this error another solution here.

Below file can have an unupdated IP address.

grep bind /etc/default/wildfly.conf

JBOSS_OPTS="-Djboss.bind.address=xx.xx.xx.xx -Djboss.bind.address.management=xx.xx.xx.xx -Djboss.management.http.port=9990 -Djboss.management.https.port=9993 -Djboss.http.port=8080 -Djboss.https.port=8443 -Djboss.ajp.port=8009"

[teknopaul]

Just for the record

everything under 127.  should be the localhost interface and you should be able to bind to it.  You dont have to do anything special for this to work in most operating systems.

e.g. this on windows

new ServerSocket().bind(new InetSocketAddress("127.0.2.1", 8080));



λ netstat -an | grep 8080

  TCP    127.0.2.1:8080         0.0.0.0:0              LISTENING