We have an EJB client application written in Java that uses RMI to communicate to Weblogic server 6.0. It initialy loads a bunch of data locally by maiing calls to the RMI server (which in turn calls session beans to retrieve the data). This has worked great "in the lab" and even "in the wild" for a while. But now we're seeing weird unexpected java RMI exceptions like "EOFException" and "PeerGoneException". Some people here claim that RMI is not a suitable protocol for such an application and that it must be timing out or is too sensitive to internet noise. Any opinions? John
posted 14 years ago
We've ameliorated the errors somewhat by implementing a retry loop of a failed RMI call. We retry the call 3 times if it fails with a RemoteException (and a couple of other exception types). This seems to greatly lessen the failures.