The IOS platform does not lend itself to launching additional processes, such as the rmid, therefore rmid must be run on another host for testing. This creates a problem for the JCK RMI ActivationSystem interface tests because Oracle's implementation of rmid as noted in section 7.4.2 of the RMI specification throws an exception when the ActivationSystem interface is access from a remote host.

We could change Oracle rmid implementation to pass the JCK, if the note was clarified to be Oracle specific rmid behaviour (one could imagine a alternative SSL based rmid that allowed remote activation management) and an new option noted to allow a single client to remotely access the interface.