Problem with hostname resolution

To run correctly SORCER needs a properly setup network configuration, in particular, it is very important for the JVM to able to resolve your hostname to a correct IP address - most probably not a loopback interface (127.x.x.x). Sorcer reads the sorcer.env file located in SORCER_HOME/configs and sets the hostname for the codeserver (webster) according to the provider.webster.interface property. By default it is set to ${localhost}. This value is automatically substituted during the Sorcer booting process by your hostname. Sometimes, in particular, on Linux hosts the default /etc/hosts file maps your hostname to your loopback interface. In that case Sorcer may run into problems finding the codeserver. Therefore please make sure your /etc/hosts resolves your hostname to your external IP.

A similar situation might occur if you invoke a service on the network and the machines involved cannot resolve their partner’s hostnames to the correct IP addresses. If you have no DNS or reverse DNS server in your network please set these hostnames in the /etc/hosts files of all involved hosts.

If your machine has multiple IP addresses you may force Sorcer to use a particular one by setting provider.webster.interface to the chosen IP address. In case you want to run offline you can set it to your loopback address, but remember to change it when you are back online since it will prevent your local Sorcer services from communicating with any other services on your network.

Java GUI in VirtualBox Guest

If you’re running a windows guest inside a VirtualBox host you may run into problems executing any Java GUIs. It results from problems with the way Java handles 3D calls. A workaround is to set the following env variable in your system: set J2D_D3D=false

Back to top

Version: 1.0. Last Published: 2014-10-15.