Support Forums: Message List - Caching EJB Home references

Caching EJB Home references

Thu, 30 Aug 2012 11:54:13 -0400

The remote home is, for all due effects a CORBA remote reference (or an encapsulated bridge thereof). As is the Remote EJB reference. This means that a PortableRemoteObject.narrow(object,homeOrRemoteClass) should actually invoke at least one CORBA...

Caching EJB Home references

Wed, 22 Jan 2003 04:20:03 -0500

...

Caching EJB Home references

Wed, 22 Jan 2003 02:49:22 -0500

As far as I know, the only way to detect a stale EJBHome is to test it by calling EJBHome.create().

Caching EJB Home references

Tue, 21 Jan 2003 23:34:12 -0500

You seem to suggest that the only way to check if a home reference is stale is to check if it is null....

Caching EJB Home references

Tue, 21 Jan 2003 16:38:47 -0500

Yes, that's the basic idea. We only catch the two exceptions mentioned above, any other exception is wrapped and rethrown to the client. Though, I can't remember where I've read that these are the only exceptions to be considered for stale Homes (perhaps...

Caching EJB Home references

Tue, 21 Jan 2003 08:32:48 -0500

I believe he meant something like this:...

Caching EJB Home references

Tue, 21 Jan 2003 07:22:29 -0500

Could you be more specific?

Caching EJB Home references

Tue, 21 Jan 2003 07:06:36 -0500

We call create() in some base class (a kind of a Remote factory for stateless Session Beans) and catch java.rmi.NoSuchObjectException as well as java.rmi.MarshalException. After catching one of those exceptions we do the Home lookup again. This scheme...

Caching EJB Home references

Tue, 21 Jan 2003 04:40:01 -0500

One problem with caching and reusing EJB homes involves handling stale cached homes....