-
Bug
-
Resolution: Duplicate
-
P5
-
8
-
generic
-
generic
TESTFAIL:java/rmi/Naming/legalRegistryNames/LegalRegistryNames.java
The test java/rmi/Naming/legalRegistryNames/LegalRegistryNames.java will fail if there is an RMI registry already running on the machine. The regression test TEST.ROOT file contains the line
exclusiveAccess.dirs=java/rmi/Naming
which prevents tests from running concurrently, which might cause registry port conflicts. However, if a registry is running on the machine external to the test suite, the test will fail. I'm not sure we can guarantee that a registry is *never* running on the test machines. At least, it's confusing to have this test fail if a registry happens to be running already; I had left one running on my development machine and I was surprised to see a "new" test failure.
The error is pretty obvious, but here it is:
Starting registry on default port
TEST FAILED: registry already running on test port
TestFailedException: TEST FAILED: registry already running on test port
at TestLibrary.bomb(TestLibrary.java:119)
at TestLibrary.bomb(TestLibrary.java:122)
at LegalRegistryNames.main(LegalRegistryNames.java:77)
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)
The test java/rmi/Naming/legalRegistryNames/LegalRegistryNames.java will fail if there is an RMI registry already running on the machine. The regression test TEST.ROOT file contains the line
exclusiveAccess.dirs=java/rmi/Naming
which prevents tests from running concurrently, which might cause registry port conflicts. However, if a registry is running on the machine external to the test suite, the test will fail. I'm not sure we can guarantee that a registry is *never* running on the test machines. At least, it's confusing to have this test fail if a registry happens to be running already; I had left one running on my development machine and I was surprised to see a "new" test failure.
The error is pretty obvious, but here it is:
Starting registry on default port
TEST FAILED: registry already running on test port
TestFailedException: TEST FAILED: registry already running on test port
at TestLibrary.bomb(TestLibrary.java:119)
at TestLibrary.bomb(TestLibrary.java:122)
at LegalRegistryNames.main(LegalRegistryNames.java:77)
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)
- duplicates
-
JDK-8005619 TEST_BUG: java/rmi/Naming/legalRegistryNames/LegalRegistryNames.java failing intermittently
- Open