JDK-8030175 : java/rmi/registry/altSecurityManager/AltSecurityManager.java fails due to timeout
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.rmi
  • Affected Version: 7u111,8
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2013-12-16
  • Updated: 2023-08-01
  • Resolved: 2017-01-09
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 8 JDK 9
8u401Fixed 9 b152Fixed
Related Reports
Duplicate :  
JDK-7161504 - TEST_BUG: java/rmi/registry/altSecurityManager/AltSecurityManager.java test fails
Relates :  
JDK-8172314 - java/rmi/registry/altSecurityManager/AltSecurityManager.java fails with "port in use"
Relates :  
JDK-7161504 - TEST_BUG: java/rmi/registry/altSecurityManager/AltSecurityManager.java test fails
Description
TESTFAIL:java/rmi/registry/altSecurityManager/AltSecurityManager.java

java/rmi/registry/altSecurityManager/AltSecurityManager.java 

Regression test for bug 4183202

expecting RuntimeException for checkListen in child process
starting sun.rmi.registry.RegistryImpl
JAVAVM: command = [/Users/aurora/sandbox/jdk/jre/bin/java, -Djava.security.manager=TestSecurityManager, sun.rmi.registry.RegistryImpl, 50466]
waited 2581 millis for sun.rmi.registry.RegistryImpl to die
sun.rmi.registry.RegistryImpl terminated on time
expecting RuntimeException for checkListen in child process
starting sun.rmi.server.Activation
JAVAVM: command = [/Users/aurora/sandbox/jdk/jre/bin/java, -Djava.security.manager=TestSecurityManager, sun.rmi.server.Activation, -port, 50468]
waited 15005 millis for sun.rmi.server.Activation to die
RMID: getting a reference to the activation system
RMID: could not contact registry while trying to shutdown activation system
TEST FAILED: reference to the activation system was null
RMID: caught exception trying to shutdown rmid
RMID: TEST FAILED: reference to the activation system was null
TestFailedException: TEST FAILED: reference to the activation system was null
	at TestLibrary.bomb(TestLibrary.java:121)
	at TestLibrary.bomb(TestLibrary.java:124)
	at RMID.shutdown(RMID.java:291)
	at AltSecurityManager.ensureExit(AltSecurityManager.java:111)
	at AltSecurityManager.main(AltSecurityManager.java:134)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:483)
	at com.sun.javatest.regtest.MainWrapper$MainThread.run(MainWrapper.java:94)
	at java.lang.Thread.run(Thread.java:744)
RMID: testlibrary finished shutting down rmid
TEST FAILED: sun.rmi.server.Activation took too long to die...
TEST FAILED: 
Test failed with: TEST FAILED: sun.rmi.server.Activation took too long to die...
TestFailedException: TEST FAILED: sun.rmi.server.Activation took too long to die...
	at TestLibrary.bomb(TestLibrary.java:121)
	at TestLibrary.bomb(TestLibrary.java:124)
	at AltSecurityManager.ensureExit(AltSecurityManager.java:114)
	at AltSecurityManager.main(AltSecurityManager.java:134)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:483)
	at com.sun.javatest.regtest.MainWrapper$MainThread.run(MainWrapper.java:94)
	at java.lang.Thread.run(Thread.java:744)
TestFailedException: TEST FAILED: ; nested exception is: 
	TestFailedException: TEST FAILED: sun.rmi.server.Activation took too long to die...
TestFailedException: TEST FAILED: sun.rmi.server.Activation took too long to die...
	at TestLibrary.bomb(TestLibrary.java:121)
	at TestLibrary.bomb(TestLibrary.java:124)
	at AltSecurityManager.ensureExit(AltSecurityManager.java:114)
	at AltSecurityManager.main(AltSecurityManager.java:134)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:483)
	at com.sun.javatest.regtest.MainWrapper$MainThread.run(MainWrapper.java:94)
	at java.lang.Thread.run(Thread.java:744)

JavaTest Message: Test threw exception: TestFailedException: TEST FAILED: ; nested exception is: 
	TestFailedException: TEST FAILED: sun.rmi.server.Activation took too long to die...
JavaTest Message: shutting down test
Comments
URL: http://hg.openjdk.java.net/jdk9/jdk9/jdk/rev/d257d5a41c58 User: lana Date: 2017-01-11 20:48:03 +0000
11-01-2017
URL: http://hg.openjdk.java.net/jdk9/dev/jdk/rev/d257d5a41c58 User: mli Date: 2017-01-09 07:19:39 +0000
09-01-2017
use RMID and REGISTRY to refactor the test to avoid potential "port in use" bug. scale the timeout value by factor.
20-12-2016
plan to fix
16-12-2016
RULE "java/rmi/registry/altSecurityManager/AltSecurityManager.java" Exception TestFailedException: TEST FAILED: sun.rmi.registry.RegistryImpl took too long to die...
22-03-2016
Is this a duplicate of JDK-7161504?
18-12-2013