Auto discovery results not cached --------------------------------- Key: JBNAME-52 URL: https://issues.jboss.org/browse/JBNAME-52 Project: JBoss Naming Issue Type: Bug Components: jnpserver Affects Versions: 5.0.3.GA Reporter: Dennis Reed When using auto-discovery to find a server, the results are not cached. Every new InitialContext sends a multicast discovery request and waits for the results. This can cause a performance problem when lots of contexts are created. org.jnp.interfaces.NamingContext has the plumbing already implemented for caching the results. It just needs a call to setHANamingServerForPartition in discoverServer to cache the discovery results, and calls to removeHANamingServerForPartition to invalidate the cache entry at the appropriate places. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira