it is the NamingServer stub that is cached, not the initial context. anyhow, I have the same problem: when i perform some JNDI operations on an initial context/subcontext, close the initialcontext via close(), and create a new initial context with the same target server as before und make a lookup on it, I receive the same kind of exception as the Naming object is still cached in org.jnp.NamingContext. If I wait some minutes before trying to perform this lookup, everythings fine, as the cache seems to be cleared again.
As a bad solution I'm making a test lookup on the initial context a priori, which makes the NamingContext remove the invalid stub if an exception is thrown. Does someone know when this cache is cleared and how I can control it? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3920443#3920443 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3920443 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
