In JDK1.4.1, HTTP fallback was made more configurable so that if the
property sun.rmi.transport.proxy.eagerHttpFallback is set to "true" then
HTTP fallback behavior will be triggered if any SocketException is thrown
by an initial direct connection attempt.
The current specification (section 3.5.2) should be loosened to specify that
fallback behavior is allowed on exceptions other than the current (more strict)
specification stating that fallback to HTTP is done only if the direct
connection attempt throws a java.net.NoRouteToHostException or a
java.net.UnknownHostException.
property sun.rmi.transport.proxy.eagerHttpFallback is set to "true" then
HTTP fallback behavior will be triggered if any SocketException is thrown
by an initial direct connection attempt.
The current specification (section 3.5.2) should be loosened to specify that
fallback behavior is allowed on exceptions other than the current (more strict)
specification stating that fallback to HTTP is done only if the direct
connection attempt throws a java.net.NoRouteToHostException or a
java.net.UnknownHostException.
- duplicates
-
JDK-4661706 (fmspec) reword specification of HTTP fallback behavior in RMI spec
-
- Resolved
-