org.evosuite.rmi

Class UtilsRMI

java.lang.Object

org.evosuite.rmi.UtilsRMI

public class UtilsRMI
extends Object

Constructor Summary

Constructors

Constructor and Description
UtilsRMI()

Method Summary

Modifier and Type	Method and Description
static void	ensureRegistryOnLoopbackAddress() A registry is created on the "localhost".
static Remote	exportObject(Remote obj) This is a wrapper over UnicastRemoteObject.exportObject, as it does not properly handle anonymous/ephemeral ports.

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Detail

UtilsRMI

public UtilsRMI()

Method Detail

exportObject

public static Remote exportObject(Remote obj)
                           throws RemoteException

This is a wrapper over UnicastRemoteObject.exportObject, as it does not properly handle anonymous/ephemeral ports. In particular, "exportObject(Remote obj)" returns a RemoteStub, and not a Remote reference.

Parameters:

obj -

Returns:

Throws:

RemoteException

ensureRegistryOnLoopbackAddress

public static void ensureRegistryOnLoopbackAddress()

A registry is created on the "localhost". But what is the "localhost"? usually, this is a loopback address 127.0.0.1. But, if there are network interfaces, depending on the operating system the "localhost" can bind to them.

So, if we start EvoSuite with a connection on (eg WiFi), losing such connection would mess up EvoSuite. Even worse, if EvoSuite is started from Eclipse, Eclipse will always use the binding it used at it start! In that case, Eclipse would need to be restarted each time connection change.

For these reasons, here we try to force to always bind to 127.0.0.1