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).
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).
- duplicates
-
JDK-4252428 java.rmi.Naming defaults port 1099 is not used.
-
- Closed
-
- relates to
-
-
- Resolved
-