Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-4508146

Minor Tweeks in NamingContext.resolve() would improve the performance by 70%

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: P3 P3
    • 1.4.0
    • 1.4.0
    • other-libs
    • None
    • beta3
    • sparc
    • solaris_8
    • Verified

      J2EE RI found out that we make a remote resolve calls if the naming context is local to the Name Server, when there are multiple name component. For example resolving a 3 level name component like "Name1/Name2/ObjectName" would result in 3 remote resolve calls instead of 1 remote call from the client. This optimization is important because JNDI look ups are pretty common in J2EE calls.

      ********************************************************************************
      ###@###.### 2001-11-19

      - Fix verified OK
        - With build: j2sdk-1_4_0-rc-bin-b86-solsparc-14_nov_2001
        - With test: /java/idl/ws/rip/RIP_TEST_MASTER/tests/api/ins/Binding/Resolve
      ********************************************************************************

            hputtaswsunw Hemanth Puttaswamy (Inactive)
            hputtaswsunw Hemanth Puttaswamy (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: