|
Quick Lists
|
|
Bug ID:
|
6666698
|
|
Votes
|
0
|
|
Synopsis
|
EnableBiasedLocking with BiasedLockingStartupDelay can block Watcher thread
|
|
Category
|
hotspot:runtime_system
|
|
Reported Against
|
|
|
Release Fixed
|
hs12(b02)
|
|
State
|
10-Fix Delivered,
bug
|
|
Priority:
|
3-Medium
|
|
Related Bugs
|
5014723
,
6539290
,
6667833
,
6686407
,
6692235
|
|
Submit Date
|
22-FEB-2008
|
|
Description
|
When run with -XX:+CacheTimeMillis the attached testcase appears to lose time because the cached time is not getting updated after ~4 seconds into the run.
It is caused by the following. The EnableBiasedLocking PeriodicTask runs on the Watcher thread when BiasedLockingStartupDelay > 0. It attempts to synchronously reach a safepoint, blocking the watcher thread, after the delay. If a safepoint cannot be reached relatively quickly, since CacheTimeMillis relies on a responsive watcher thread, the cached time may not get updated promptly.
Posted Date : 2008-02-22 16:14:57.0
|
|
Work Around
|
N/A
|
|
Evaluation
|
Fix per comments.
Posted Date : 2008-02-22 16:14:57.0
|
|
Comments
|
PLEASE NOTE: JDK6 is formerly known as Project Mustang
|
|
|
|
