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

java.net.URI does not parse literal IPv4 + explicit port URIs properly

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: P2
    • Resolution: Fixed
    • Affects Version/s: 1.4.0
    • Fix Version/s: 1.4.0
    • Component/s: core-libs
    • Labels:
    • Subcomponent:
    • Resolved In Build:
      beta
    • CPU:
      sparc
    • OS:
      solaris_1

      Description

      Build tested against: Merlin b57

      The java.rmi.Naming.lookup(url) call performs a lookup against the localhost even though the specified url points to a different host.

      This is evident from the client logs attached. In case of the b57 logs, the URL that is specified points to 129.144.250.194:9000/DGCTestServer, but it appears to be doing a lookup against 129.144.250.205, the localhost in this case.

      However, the same test passes against build b56, as seen in the client log for this build.

      For further details about the test case, please contact me at x53492 or Muthu at X53517

        Attachments

          Activity

            People

            • Assignee:
              ywangsunw Yingxian Wang (Inactive)
              Reporter:
              nkesavansunw Nandkumar Kesavan (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:
                Imported:
                Indexed: