|
Quick Lists
|
|
Bug ID:
|
6561443
|
|
Votes
|
0
|
|
Synopsis
|
Timeout on synchronized blocks
|
|
Category
|
hotspot:runtime_system
|
|
Reported Against
|
|
|
Release Fixed
|
|
|
State
|
3-Accepted,
request for enhancement
|
|
Priority:
|
5-Very Low
|
|
Related Bugs
|
|
|
Submit Date
|
23-MAY-2007
|
|
Description
|
A DESCRIPTION OF THE REQUEST :
Within bug id 4140870 a request was formulated for timeout on synchronized blocks. The solution proposed was to use concurrent.locks.ReentrantLocks.
This is not always applicable:
In case of third party libraries we have no way of changing the code from synchronized(){} to use the concurrent package.
We therefore request to add a VM attribute for example -DdeadlockTimeout, which would throw an exception if a dead lock is encountered for longer than a given time period.
JUSTIFICATION :
In case of third party libraries we have no way of changing the code from synchronized(){} to use the concurrent package.
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
We therefore request to add a VM attribute for example -DdeadlockTimeout, which would throw an exception if a dead lock is encountered for longer than a given time period.
ACTUAL -
Currently the application just hangs.
Posted Date : 2007-05-23 22:39:53.0
|
|
Work Around
|
N/A
|
|
Evaluation
|
N/A
|
|
Comments
|
PLEASE NOTE: JDK6 is formerly known as Project Mustang
|
|
|
 |