JDK-6776144 : java/lang/ThreadGroup/NullThreadName.java fails with Thread group is not destroyed ,fastdebug LINUX
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.lang
  • Affected Version: 7
  • Priority: P4
  • Status: Closed
  • Resolution: Fixed
  • OS: linux
  • CPU: generic
  • Submitted: 2008-11-25
  • Updated: 2013-12-17
  • Resolved: 2012-05-07
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.
7u21Fixed 8 b15Fixed
java/lang/ThreadGroup/NullThreadName.java fails in fastdebug mode on linux-amd64
command: main NullThreadName
reason: Assumed action based on file name: run main NullThreadName 
elapsed time (seconds): 0.716
OK, caught expected java.lang.NullPointerException: name cannot be null
Good Thread started...
Good Thread finishing
java.lang.AssertionError: Failed: Thread group is not destroyed.
	at NullThreadName.main(NullThreadName.java:72)
	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:623)
	at com.sun.javatest.regtest.MainWrapper$MainThread.run(MainWrapper.java:94)
	at java.lang.Thread.run(Thread.java:713)

originally failed with -server -Xmixed, but fails with -client too.

EVALUATION This test waits 10 seconds for threads to terminate, but on a busy or slow system, this may not be sufficient. Since the outer jtreg harness allows for 120 seconds before terminating a test, there's no reason for the test to be more restrictive.