-
Bug
-
Resolution: Fixed
-
P4
-
1.2.0, 1.2.2
-
012
-
generic, sparc
-
generic, solaris_8
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2022289 | 1.3.0 | Michael Warres | P4 | Resolved | Fixed | beta |
JDK-2022288 | 1.2.2_12 | Michael Warres | P4 | Resolved | Fixed | 12 |
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.
- backported by
-
JDK-2022288 ObjectStreamClass can hold global lock for a very long time
- Resolved
-
JDK-2022289 ObjectStreamClass can hold global lock for a very long time
- Resolved
- duplicates
-
JDK-4521042 Object serialization very slow in jdk 1.2.2 during concurrent user loads
- Closed