java.rmi.activation.activator.class java.rmi.activation.port sun.rmi.activation.execTimeout sun.rmi.activation.snapshotInterval sun.rmi.rmid.maxstartgroup

The Activation Framework has six configurable parameters that will help you tweak various aspects of its behavior. Two of them are part of the Java standard, and four are specific to Suns implementation of the activatable classes. The parameters are: java.rmi.activation.activator.class java.rmi.activation.port sun.rmi.activation.execTimeout sun.rmi.activation.snapshotInterval sun.rmi.rmid.maxstartgroup sun.rmi.server.activation.debugExec .

17.6.6.1 java.rmi.activation.activator.class

This is the implementation class that the activation system should use to instantiate the Activator interface. The default value is sun.rmi.server.ActivationActivatorImpl . It is extremely rare that this property is overridden.

17.6.6.2 java.rmi.activation.port

This is the port on which rmid will listen for incoming remote calls. The default value is 1098. This value is used by both rmid it is the default for the -port command-line argument and by the launch code that registers instances of ActivationDesc with rmid . If you decide to use a different port for your launch code, then you also need to set -port for rmid and vice-versa.

17.6.6.3 sun.rmi.activation.execTimeout

This is the time, in milliseconds, that the activation system will wait for a spawned activation group to start up. The default value is 30,000 ms 30 seconds. Because the activation group and the activation daemon are on the same server, there are no network latency issues involved in this timeout. Hence, this is another property that rarely needs to be changed.

17.6.6.4 sun.rmi.activation.snapshotInterval

In addition to its log, rmid also occasionally creates a snapshot of all of its entries. These snapshots are stored in the log directory and used by rmid to recover from crashes. That is, if rmid stops executing and is then restarted, it can automatically recover. You dont need to recreate all the entries. sun.rmi.activation.snapshotInterval controls how often the activation daemon writes to its log file. Instead of writing to the log file every time something happens, the activation daemon waits for sun.rmi.activation.snapshotInterval s many operations to happen before writing a new snapshot. An operation is defined as something that changes the number of registered servers or the number of active servers. Starting up, or shutting down, a server counts as an operation; renewing a lease does not. The default value for sun.rmi.activation.snapshotInterval is 200 operations.

17.6.6.5 sun.rmi.rmid.maxstartgroup

rmid needs to occasionally launch JVMs, such as when a server is required, but the JVM for that server has not yet been launched. This parameter sets a limit on the maximum number of JVMs that rmid will be in the process of launching at any given time. Note that this is not a limit on the number of JVMs launched by the activation daemon. Instead, its just a limit on how many are being launched concurrently. The idea is to smooth out system performance by preventing a large number of really costly operations such as spawning a JVM from occurring at the same time. The default value for sun.rmi.rmid.maxstartgroup is 3 ms.

17.6.6.6 sun.rmi.server.activation.debugExec