While trying to start an Infinspan server on my virtual machine with NAT as network connection, the startup script failed with the following exception:
[org.jboss.msc.service.fail] (MSC service thread 1-7) 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.2.0.Final.jar:7.2.0.Final] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.4.GA.jar:1.0.4.GA] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.4.GA.jar:1.0.4.GA] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25] at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25]
To solve this problem, you need to configure the IP address of the virtual machine as bind parameter within the startup as outlined here:
Instead of starting with
./standalone.sh
you must start the server with
./standalone.sh -b xxx.xxx.xx.xxx
If you have a cluster, instead of starting with
./cluster.sh
you must start the server with
./cluster.sh -b xxx.xxx.xx.xxx
Einsortiert unter:Build, config and deploy Tagged: Infinispan, Network, vmware
![](http://stats.wordpress.com/b.gif?host=blog.oio.de&blog=7731718&post=6420&subd=techscouting&ref=&feed=1)