3.7.3.5.6.1 Problem Statement
- You write SERVER1 such that all objects on interface A are
preactivated. To prevent the object from being activated on demand
by the TP Framework, you write the interface's
activate_object
method to always throw theActivateObjectFailed
exception. - SERVER2 also implements objects of interface A. However, instead of preactivating the objects, SERVER2 lets the TP Framework activate them on demand.
- If the administrator configures SERVER1 and SERVER2 in the same
group, then a client can get an interface A object reference from
SERVER2 and invoke on it. Then, due to load balancing, SERVER1
could be asked to activate an object on interface A. However,
SERVER1 is not able to activate an object on interface A on demand
because its
activate_object
method throws theActivateObjectFailed
exception.
Parent topic: Caution