Uploaded image for project: 'JBoss Naming'
  1. JBoss Naming
  2. JBNAME-52

Auto discovery results not cached

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • 5.0.3.GA
    • jnpserver
    • None
    • Workaround Exists
    • Hide

      Cache the InitialContext in the client.
      This is only triggered when a new InitialContext is created.

      Show
      Cache the InitialContext in the client. This is only triggered when a new InitialContext is created.

      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.

            Unassigned Unassigned
            rhn-support-dereed Dennis Reed
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: