It is not designed, however, to provide persistent access to data since simultaneous failure of the primary and backup servers cannot be recovered. Entity beans should always manage persistent data. Node C, request forwarding, in Figure 1 represents this. Home Stub - This object is the first object accessed by remote clients and runs locally on a client's virtual machine. Since stubs and skeletons are typically generated by EJB compilers at deployment time, the underlying logic in a stub can be vendor-specific.
Vendors can instrument some method-level load balancing and failover schemes directly in the stub.
Since the primary action of the home stub is to create or load beans on a remote server, the server in which a bean is ultimately created is not important. Node D in Figure 1 represents this. Remote Stub - This object is instantiated by the home skeleton and returned back to the client. This object can perform the same types of load balancing and failover that a home stub can do, but vendors have to be careful about when they choose to do so. For instance, if a client has created an entity bean, it is likely that the entity bean will only exist in one server in the cluster.