Interesting question. The references to an entity bean will still be valid (required by the EJB Spec).
I would expect stateless session bean references to be valid as well. I would be interested in hearing if this does not hold true for other vendors. And lastly, stateful session beans are bit more trickier. I would expect these references to be invalid for most other vendors. The EJB spec seems to mention Handles only - not references to session beans. <vendor> The references held (by clients) to entity beans, stateless and stateful session beans are valid even if the server has been restarted. The same applies to a cluster as well. An AppServer in a cluster can re-create object instances in its own VM (as a result of methods invoked by clients on the references) if another instance in the cluster is unavailable. Thus, server failovers are transparent to the client. </vendor> The above mentioned capability comes to you 'free'. That is, there is no requirement of recompiling stubs/skeletons/clients to make them 'cluster/failover aware'. -krish > -----Original Message----- > From: A mailing list for Enterprise JavaBeans development > [mailto:[EMAIL PROTECTED]]On Behalf Of Venkata Reddy Vajrala > Sent: Wednesday, February 13, 2002 2:32 PM > To: [EMAIL PROTECTED] > Subject: EJBHome Factory - Home Object Caching > > > You have to use an ordinary Java class(not an ejb) as ejb home factory > as explained in "EJBHome factory design pattern" available for review at > > http://www.theserverside.com/patterns/index.jsp > > But I got one doubt after reading that document. The cached homes will > throw an exception if the ejb server is down for some time and then up. > What could be the > workaround for this problem? The client using the cached ejb home > cannot get the reference and store it in the factory. Any ideas? > > thanks in advance. > > Giju Thomson wrote: > > Hi All , > > I have found out that the most time taken in a ejb lifecycle is at > JDNI Lookup . So if we can cache the home object then it will be much > faster . How can we > cache the home object ? What is the best algo to implement a object > cache . Which would be better the cache as a MBean or as a SessionBean ? > > Thanking you in advance . > > Cheers > > Thomson > > =========================================================================== > To unsubscribe, send email to [EMAIL PROTECTED] and include in the body > of the message "signoff EJB-INTEREST". For general help, send email to > [EMAIL PROTECTED] and include in the body of the message "help". > > =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
