|
Quick Lists
|
|
Bug ID:
|
4165204
|
|
Votes
|
1
|
|
Synopsis
|
ObjectStreamClass can hold global lock for a very long time
|
|
Category
|
java:serialization
|
|
Reported Against
|
1.2.2
, 1.2fcs
|
|
Release Fixed
|
1.2.2_012,
1.2.2_12(Bug ID:2022288)
, 1.3(kestrel-beta) (Bug ID:2022289)
|
|
State
|
10-Fix Delivered,
bug
|
|
Priority:
|
4-Low
|
|
Related Bugs
|
4521042
|
|
Submit Date
|
10-AUG-1998
|
|
Description
|
ObjectStreamClass has a global descriptorFor that all calls to lookupInternal synchronize on. The code executed inside this synchronized can cause classes to be loaded, from arbitrary URLs with arbitrary network delays. If one thread is stuck in this synchronized block attempting to read from a slow or non-responsive network connection, then all other threads that are attempting to serialize or deserialize are also stuck for the duration. This can be a serious performance limitation for RMI.
|
|
Work Around
|
N/A
|
|
Evaluation
|
A fix is coded, but it was decided that it was too late too add it now.
The diff for the fix and the actual file containing the fix has been
added to the attachments.
xxxxx@xxxxx 1998-09-03
|
|
Comments
|
PLEASE NOTE: JDK6 is formerly known as Project Mustang
|
|
|
|
