JDK-6716076 : test UTIL_REGRESSION/test/java/util/logging/LoggingDeadlock2.java failed with exit code 1
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.util.logging
  • Affected Version: 7
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2008-06-18
  • Updated: 2010-04-02
  • Resolved: 2009-04-25
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 7 Other
7 b57Fixed OpenJDK6Fixed
Related Reports
Relates :  
JDK-6467152 - deadlock occurs in LogManager initialization and JVM termination
Relates :  
JDK-6829636 - test/java/util/logging/LoggingDeadlock2.java is flaky
Description
Test java/util/logging/LoggingDeadlock2.java from UTIL_REGRESSION calls System.exit(1) which is detected by jtreg harness as failed test.

Test output
Test passed
----------System.err:(0/0)----------
result: Failed. Unexpected exit from test [exit code: 1]

It reproduces with any java release on any platform.
Comments
EVALUATION Calling System.exit() is a required part of this .java program. The solution is to create a shell script and make that the actual jtreg @test.
29-07-2008
EVALUATION jtreg tests should not be calling System.exit() at all
29-07-2008
SUGGESTED FIX Replace System.exit(1); by System.exit(0); as there is no differece for the test.
18-06-2008