This week's giveaway is in the EJB and other Java EE Technologies forum. We're giving away four copies of EJB 3 in Action and have Debu Panda, Reza Rahman, Ryan Cuprak, and Michael Remijan on-line! See this thread for details.
One problem with caching and reusing EJB homes involves handling stale cached homes. If a client caches an EJB home and the container shuts down and then returns, the client�s cached value is stale and will not work, resulting in a CORBA exception. Is there any strategy wherein one could check whether the cached EJB Home reference is stale?
This is really dependent on your Application Server. Many Application Servers implement the Home stubs in such a way that they can survive server crashes, restarts, and hot redeployments. Furthermore, Home stubs are typically implemented in a cluster-aware fashion so that a Home stub is also not tied to a single node if you are running in a clustered environment. Again this is highly dependent on your Application Server, check there first.