-
Bug
-
Resolution: Fixed
-
P4
-
hs20
-
b68
-
b143
-
generic
-
generic
-
Verified
The test
nsk/logging/stress/threads/scmhml001
failed in JDK 7 b124 (HS 20.0-b05) promotion testing with the following message:
[2011-01-11T22:31:42.19] # Actual: C:/local/common/jdk/baseline/windows-i586/bin/java -server -Xcomp -XX:+StartAttachListener -XX:+UseParallelGC nsk.logging.stress.threads.scmhml001 25 25 25
[2011-01-11T22:31:42.19] # Test level exit status: 151
[2011-01-11T23:01:43.30] # Cygwin watchdog kill: 9740 4936
[2011-01-11T23:01:43.49] Exception in thread "main" java.lang.NullPointerException
[2011-01-11T23:01:43.55] at nsk.logging.stress.threads.scmhml001.doTest(scmhml001.java:81)
[2011-01-11T23:01:43.55] at nsk.logging.stress.threads.scmhml001.run(scmhml001.java:53)
[2011-01-11T23:01:43.55] at nsk.logging.stress.threads.scmhml001.main(scmhml001.java:31)
[2011-01-11T23:01:43.55] # Host info: CYGWIN_NT-5.2-WOW64 vmsqe-p4-04 1.5.25(0.156/4/2) 2008-06-12 19:34 i686 Cygwin
http://vmsqe.russia.sun.com/execution/results/JDK7/PROMOTION/VM/7/b124/ParallelGC/vm/windows-i586/server/comp/windows-i586_vm__server_comp_nsk.logging.testlist/ResultDir/scmhml001/scmhml001.log
The test appeares to hang, because by the time the main thread dies of NPE, it has started a number of handler threads that seat and wait in socket reads.
Platform: windows-i586
Machine: vmsqe-p4-04.russia.sun.com
Options: -server -Xcomp -XX:+StartAttachListener -XX:+UseParallelGC
Relevant part of the test code:
73 for (int n=0; n<controllers.length; n++) {
74 controllers[n] = new SocketController();
75 Handler handler = controllers[n].getHandler();
76
77 for (int i=0; i<loggers.length; i++) {
78 String name_n_i = testName.replace('/','.')
79 + ".logger_" + n + "_" + i;
80 loggers[n][i] = Logger.getLogger(name_n_i);
81 loggers[n][i].addHandler(handler);
82 loggers[n][i].setLevel(Level.FINEST);
83 //
84 threads[n][i] = new MyThread(n,i,loggers[n][i]);
85 };
86 };
Apparently, Logger.getLogger(name_n_i) returned null.
nsk/logging/stress/threads/scmhml001
failed in JDK 7 b124 (HS 20.0-b05) promotion testing with the following message:
[2011-01-11T22:31:42.19] # Actual: C:/local/common/jdk/baseline/windows-i586/bin/java -server -Xcomp -XX:+StartAttachListener -XX:+UseParallelGC nsk.logging.stress.threads.scmhml001 25 25 25
[2011-01-11T22:31:42.19] # Test level exit status: 151
[2011-01-11T23:01:43.30] # Cygwin watchdog kill: 9740 4936
[2011-01-11T23:01:43.49] Exception in thread "main" java.lang.NullPointerException
[2011-01-11T23:01:43.55] at nsk.logging.stress.threads.scmhml001.doTest(scmhml001.java:81)
[2011-01-11T23:01:43.55] at nsk.logging.stress.threads.scmhml001.run(scmhml001.java:53)
[2011-01-11T23:01:43.55] at nsk.logging.stress.threads.scmhml001.main(scmhml001.java:31)
[2011-01-11T23:01:43.55] # Host info: CYGWIN_NT-5.2-WOW64 vmsqe-p4-04 1.5.25(0.156/4/2) 2008-06-12 19:34 i686 Cygwin
http://vmsqe.russia.sun.com/execution/results/JDK7/PROMOTION/VM/7/b124/ParallelGC/vm/windows-i586/server/comp/windows-i586_vm__server_comp_nsk.logging.testlist/ResultDir/scmhml001/scmhml001.log
The test appeares to hang, because by the time the main thread dies of NPE, it has started a number of handler threads that seat and wait in socket reads.
Platform: windows-i586
Machine: vmsqe-p4-04.russia.sun.com
Options: -server -Xcomp -XX:+StartAttachListener -XX:+UseParallelGC
Relevant part of the test code:
73 for (int n=0; n<controllers.length; n++) {
74 controllers[n] = new SocketController();
75 Handler handler = controllers[n].getHandler();
76
77 for (int i=0; i<loggers.length; i++) {
78 String name_n_i = testName.replace('/','.')
79 + ".logger_" + n + "_" + i;
80 loggers[n][i] = Logger.getLogger(name_n_i);
81 loggers[n][i].addHandler(handler);
82 loggers[n][i].setLevel(Level.FINEST);
83 //
84 threads[n][i] = new MyThread(n,i,loggers[n][i]);
85 };
86 };
Apparently, Logger.getLogger(name_n_i) returned null.
- relates to
-
JDK-6814140 deadlock due to synchronized demandLogger() code that locks ServerLogManager
- Resolved
-
JDK-6487638 Calling LogManager.addLogger() and Logger.getLogger() cause deadlock
- Closed
-
JDK-7045441 locking analysis and other possible improvements for Logging API
- Open