Page History

...

• Got this error on client side ?

  Code Block
  Caused by: java.util.MissingResourceException: Can't find bundle for base name cache, locale en_US

• How to use RMI without SSL
• How to test easily if RMI is working (using a simple client)
• Somethings you should know about RMI

Searches

• Search in Nabble or Mark Mail OFBiz forums from Firefox 

...

1. Unzip somewhere on you disk this attachment. From there I guess it's pretty simple.

Somethings you should know about RMI

• On Windows, do not have any spaces between any directories on your path, or the RMIDispatcher will not start
• On Linux, the RMI server may not know its own IP address and might get "lost." This will cause java.net.SocketException?: Socket is not connected (Error connecting to 127.0.0.1). This error message is generated on the RMI server but it will be displayed on the RMI client. The answer is to force rmi server's IP address into the JVM envrionment (http://forum.java.sun.com/thread.jsp?forum=58&thread=288759&tstart=0&trange=15):^{Image Added}

The canonical server-side solution appears to be to tell the server its IP on startup:

-Djava.rmi.server.hostname=111.222.333.444

or, more flexibly, something like:

-Djava.rmi.server.hostname=`ifconfig eth0.1:1|grep "inet addr:" | sed "s/inet addr://" | awk '{print $1}'`

Here's another little tidbit, if the -Djava.rmi.server.hostname isn't working and the exception is still being generated on the client (from the server) on linux try changing the order of the host names in the /etc/hosts file so that the 127.0.0.1 appears last. This is apparently due to a bug in the InetAddress.getLocalHost() method.

• Make sure that rmiregistry is not running on your RMIDispatcher/JOTM/jndi port before starting Open for Business