JDK-6454475 : NPE on solaris-i586 -server running ConcurrentQueueLoops
- Type: Bug
- Component: hotspot
- Sub-Component: compiler
- Affected Version: 6
- Priority: P1
- Status: Closed
- Resolution: Duplicate
- OS: generic
- CPU: generic
- Submitted: 2006-07-31
- Updated: 2010-08-18
- Resolved: 2006-08-01
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.
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 6 |
|---|
6Resolved  |
Related Reports
|
Duplicate :
|
|
|
Relates :
|
Description
While investigating 6454444: SEGV on solaris-i586 running ConcurrentQueueLoops it was determined that the various failure modes of that test were introduced at different times, which strongly suggests this test is catching two independent bugs. This CR is to track the NPE generated when running regtest test/java/util/concurrent/ConcurrentLinkedQueue/ConcurrentQueueLoops.java and the hang seen occasionally since b93 as well. The failures are never seen with -client. How to reproduce: (mb29450@bonsai) test/java/util/concurrent/ConcurrentLinkedQueue $ repeat 1000 time jver 6-b93 java ConcurrentQueueLoops ... Warmup... Threads: 1 :java.lang.NullPointerException at java.util.concurrent.ConcurrentLinkedQueue.poll(ConcurrentLinkedQueue.java:220) at ConcurrentQueueLoops$Stage.call(ConcurrentQueueLoops.java:62) at ConcurrentQueueLoops$Stage.call(ConcurrentQueueLoops.java:44) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907) at java.lang.Thread.run(Thread.java:619) Exception in thread "main" java.util.concurrent.ExecutionException: java.lang.Error: Call loop failed at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222) at java.util.concurrent.FutureTask.get(FutureTask.java:83) at ConcurrentQueueLoops.oneRun(ConcurrentQueueLoops.java:105) at ConcurrentQueueLoops.main(ConcurrentQueueLoops.java:39) Caused by: java.lang.Error: Call loop failed at ConcurrentQueueLoops$Stage.call(ConcurrentQueueLoops.java:85) at ConcurrentQueueLoops$Stage.call(ConcurrentQueueLoops.java:44) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907) at java.lang.Thread.run(Thread.java:619)
Comments
|