There are performance reasons leading one to implement several objects in the same process. It is relatively inexpensive for these objects to invoke each other's methods, since such an invocation does not require a context switch. Furthermore, there are serious problems in resource utilization with running multiple Java virtual machines on the same processor. Hence, one often tries to structure an OrbixWeb application with as many objects as possible in the same process.
However, per-process filters are not invoked for method invocations between objects in the same process. Hence, per-process filters can not be used to implement causal logging among objects in the same process. This implies that each COPE optimist must run in its own process. This solution carries an enormous performance penalty.