-
Bug
-
Resolution: Won't Fix
-
P4
-
7, 8, 9
-
generic
-
generic
TESTFAIL:sun/rmi/transport/proxy/EagerHttpFallback.java
The test sun/rmi/transport/proxy/EagerHttpFallback.java fails consistently for some developers on their desktop systems. Oddly, it doesn't seem to fail on JPRT or on our nightly builds.
Test log is as follows:
call on registry stub with port 35557did not successfully perform HTTP fallback to 52732
java.rmi.ConnectException: Connection refused to host: 127.0.1.1; nested exception is:
java.net.ConnectException: Connection refused
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:619)
at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:216)
at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:202)
at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:341)
at sun.rmi.registry.RegistryImpl_Stub.list(Unknown Source)
at EagerHttpFallback.main(EagerHttpFallback.java:59)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:474)
at com.sun.javatest.regtest.MainWrapper$MainThread.run(MainWrapper.java:94)
at java.lang.Thread.run(Thread.java:722)
Caused by: java.net.ConnectException: Connection refused
at sun.rmi.transport.proxy.RMIMasterSocketFactory.checkConnector(RMIMasterSocketFactory.java:320)
at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:266)
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:613)
... 11 more
The test sun/rmi/transport/proxy/EagerHttpFallback.java fails consistently for some developers on their desktop systems. Oddly, it doesn't seem to fail on JPRT or on our nightly builds.
Test log is as follows:
call on registry stub with port 35557did not successfully perform HTTP fallback to 52732
java.rmi.ConnectException: Connection refused to host: 127.0.1.1; nested exception is:
java.net.ConnectException: Connection refused
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:619)
at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:216)
at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:202)
at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:341)
at sun.rmi.registry.RegistryImpl_Stub.list(Unknown Source)
at EagerHttpFallback.main(EagerHttpFallback.java:59)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:474)
at com.sun.javatest.regtest.MainWrapper$MainThread.run(MainWrapper.java:94)
at java.lang.Thread.run(Thread.java:722)
Caused by: java.net.ConnectException: Connection refused
at sun.rmi.transport.proxy.RMIMasterSocketFactory.checkConnector(RMIMasterSocketFactory.java:320)
at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:266)
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:613)
... 11 more
- relates to
-
JDK-8066750 Remove HTTP proxy implementation and tests from RMI
-
- Resolved
-
-
JDK-8155978 Remove HTTP proxy implementation and tests from RMI (again)
-
- Resolved
-
-
JDK-8157813 Remove sun/rmi/transport/proxy/EagerHttpFallback.java from ProblemList.txt
-
- Closed
-