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.