JDK-7140992 : TEST_BUG: java/rmi/server/Unreferenced/finiteGCLatency/FiniteGCLatency.java fails intermittently
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.rmi
  • Affected Version: 7u4,8,9
  • Priority: P5
  • Status: Open
  • Resolution: Unresolved
  • OS: generic,solaris_10
  • CPU: generic,sparc
  • Submitted: 2012-01-30
  • Updated: 2018-09-11
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.
Other
tbdUnresolved
Related Reports
Relates :  
Relates :  
Description
TESTFAIL:java/rmi/server/Unreferenced/finiteGCLatency/FiniteGCLatency.java

test failed on some solaris (stt-58.ru - sparc, stt-11.ru - x86) and linux (stt-52.ru, stt-82-ovm3.ru) since 7u4b06, passed with 7u4b05, 7u3b04 and 7b148

passed on other solaris stt-19.ru (sparc), stt-12.ru (x86) and windows 7 x86 (stt-70-vbx1.ru)

see comments for more details

Comments
ProblemList please
24-10-2014

Ha. This test has been failing for years, with apparently the same timeout. See JDK-4863604.
30-06-2014

Attached JTR file from this failure.
30-01-2013

It's failed again. Test log file attached.
30-01-2013

I've made all the comment history public. Nothing confidential in here.
30-01-2013

issue is not reproducible with jdk7u4b15 and jdk7u5b01 jdk 7u4b06 testing: checked with -Xms3g - failed checked with increased to 5 minutes TIMEOUT - failed: unbound remote object from registry; waiting for unreferenced() callback... java.lang.RuntimeException: TEST FAILED: unrefereced() not invoked after 300.0 seconds
30-01-2013

Three of us in development have tried running this test and have not been able to reproduce this failure. We've tried on Solaris and Linux. I suspect it has something to do with the JVM/machine configuration issue. Possibly a heap allocation/garbage collection setting issue. Still investigating.
30-01-2013

This test is failing in JPRT too: -------------------------------------------------- TEST: java/rmi/server/Unreferenced/finiteGCLatency/FiniteGCLatency.java JDK under test: (/tmp/jprt/P2/124459.albatem/testproduct/linux_i586_2.6-product) java version "1.8.0-internal" Java(TM) SE Runtime Environment (build 1.8.0-internal-201202111244.albatem.tl-b00) Java HotSpot(TM) Server VM (build 23.0-b14, mixed mode) ACTION: build -- Passed. Build successful REASON: User specified action: run build FiniteGCLatency TIME: 0.794 seconds messages: command: build FiniteGCLatency reason: User specified action: run build FiniteGCLatency elapsed time (seconds): 0.794 ACTION: compile -- Passed. Compilation successful REASON: .class file out of date or does not exist TIME: 0.793 seconds messages: command: compile /tmp/jprt/P2/124459.albatem/source/jdk/test/java/rmi/server/Unreferenced/finiteGCLatency/FiniteGCLatency.java reason: .class file out of date or does not exist elapsed time (seconds): 0.793 STDOUT: STDERR: Note: /tmp/jprt/P2/124459.albatem/source/jdk/test/java/rmi/server/Unreferenced/finiteGCLatency/../../../testlibrary/TestLibrary.java uses or overrides a deprecated API. Note: Recompile with -Xlint:deprecation for details. Note: /tmp/jprt/P2/124459.albatem/source/jdk/test/java/rmi/server/Unreferenced/finiteGCLatency/../../../testlibrary/TestLibrary.java uses unchecked or unsafe operations. Note: Recompile with -Xlint:unchecked for details. ACTION: build -- Passed. Build successful REASON: User specified action: run build FiniteGCLatency_Stub TIME: 0.617 seconds messages: command: build FiniteGCLatency_Stub reason: User specified action: run build FiniteGCLatency_Stub elapsed time (seconds): 0.617 ACTION: compile -- Passed. Compilation successful REASON: .class file out of date or does not exist TIME: 0.617 seconds messages: command: compile /tmp/jprt/P2/124459.albatem/source/jdk/test/java/rmi/server/Unreferenced/finiteGCLatency/FiniteGCLatency_Stub.java reason: .class file out of date or does not exist elapsed time (seconds): 0.617 STDOUT: STDERR: ACTION: build -- Passed. All files up to date REASON: Named class compiled on demand TIME: 0.0 seconds messages: command: build FiniteGCLatency reason: Named class compiled on demand elapsed time (seconds): 0.0 ACTION: main -- Failed. Execution failed: `main' threw exception: java.lang.RuntimeException: TEST FAILED: unrefereced() not invoked after 50.0 seconds REASON: User specified action: run main/othervm/timeout=120 FiniteGCLatency TIME: 50.489 seconds messages: command: main FiniteGCLatency reason: User specified action: run main/othervm/timeout=120 FiniteGCLatency elapsed time (seconds): 50.489 STDOUT: STDERR: Regression test for bug 4164696 exported remote object created registry bound remote object in registry unbound remote object from registry; waiting for unreferenced() callback... java.lang.RuntimeException: TEST FAILED: unrefereced() not invoked after 50.0 seconds at FiniteGCLatency.main(FiniteGCLatency.java:98) 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) JavaTest Message: Test threw exception: java.lang.RuntimeException: TEST FAILED: unrefereced() not invoked after 50.0 seconds JavaTest Message: shutting down test STATUS:Failed.`main' threw exception: java.lang.RuntimeException: TEST FAILED: unrefereced() not invoked after 50.0 seconds TEST RESULT: Failed. Execution failed: `main' threw exception: java.lang.RuntimeException: TEST FAILED: unrefereced() not invoked after 50.0 seconds --------------------------------------------------
30-01-2013

JUSTIFICATION Priority changed from [] to [1-Very High] regression vera.akulova@oracle.com 2012-01-30 17:37:28 GMT Priority changed from [1-Very High] to [4-Low] This issue is not reproducible by development on 3 different machines using Solaris and Linux. It is also in a less-used area (RMI) and in a less-used area of RMI. darryl.mocek@oracle.com 2012-03-26 20:21:40 GMT Priority changed from [4-Low] to [3-Medium] regression in 7u4b06 vera.akulova@oracle.com 2012-04-02 14:26:31 GMT
30-01-2013

I've reopened this bug. This test still fails intermittently. It may simply need to have its timeout raised.
19-12-2012

EVALUATION This issue cannot be reproduced.
26-03-2012