JDK-8030187 : TEST_BUG: java/util/logging/Logger/setResourceBundle/TestSetResourceBundle.java failing again
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.util.logging
  • Affected Version: 8
  • Priority: P4
  • Status: Closed
  • Resolution: Fixed
  • Submitted: 2013-12-16
  • Updated: 2019-02-22
  • Resolved: 2013-12-20
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.
8u20Fixed 9 b01Fixed
Related Reports
Relates :  
Relates :  
java/util/logging/Logger/setResourceBundle/TestSetResourceBundle.java keep failing in PIT of b121 

jtr attached.

Dec 15, 2013 7:03:08 AM TestSetResourceBundle test
SEVERE: toto
Dec 15, 2013 7:03:20 AM TestSetResourceBundle test
java.lang.RuntimeException: Unexpected bundle name: resources.ListBundle
	at TestSetResourceBundle.test(TestSetResourceBundle.java:290)
	at TestSetResourceBundle.testSecure(TestSetResourceBundle.java:153)
	at TestSetResourceBundle$TestCase.run(TestSetResourceBundle.java:95)
	at TestSetResourceBundle.main(TestSetResourceBundle.java:123)
	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)
I turned on -XX:+PrintGCDetails that shows GC happened during the test run due to object allocation failure. Without -Xcomp, object allocation succeeds in the test() method body.

This is again a case of loggers being too eagerly gc'ed. Though I can't be 100% sure my analysis of the issue and my experiments with JDK-8030192 let me think that I'm right.