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

java.rmi.Naming shouldn't rely upon the parsing functionality of java.net.URL

    XMLWordPrintable

    Details

    • Subcomponent:
    • Resolved In Build:
      kestrel
    • CPU:
      sparc
    • OS:
      solaris_2.6

      Description

      java.rmi.Naming.lookup with no port specified tries to connect to port 80
      instead of Registry.REGISTRY_PORT (1099).

      The default port change from -1 to port 80 in java.net.URL causes
      java.rmi.Naming to think the port has been specified as 80 rather than being
      unspecified (-1). Previously if the port was unspecified (-1), the
      java.rmi.Naming API would use the registry's default port of 1099.

      ====

      java.net.URL will be changed to revert to the behavior it had prior to this change. java.rmi.Naming should be changed to support its own URL parsing. Since RMI supports its own simple URL syntax, RMI should take care of doing this parsing (this modification would likely make java.rmi.Naming more robust).

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              ldorninsunw Laird Dornin (Inactive)
              Reporter:
              doburns Dana Burns
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Imported:
                Indexed: