DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=42494>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=42494 Summary: local JNDI context indefinitely caches objects from custom object factories Product: Tomcat 5 Version: 5.5.17 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: Catalina AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Currently, if I locate a resource (e.g. EJB Home) from Tomcat's JNDI Context, and I have configured a custom Object Factory for that location, the factory is only exactly queried once. This is very problematic in the EJB case because if the connection to the server has been broken (for example by an application server restart), as this renders the handle invalid and there is no way to get another handle on the same bean again (apart from restarting Tomcat). This is on Tomcat 5.5.17, but is most likely broken on 5.5.23, too. Please note that Tomcats behaviour is also conflicting with the docs: "Every time your web application calls lookup() on a context entry that is bound to this factory, the getObjectInstance() method is called, ..." (quoted from JNDI resources howto, Adding custom resource factories) -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
