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.
JVMs are deadlocked waiting on resources deep in the Java environment in ObjectStreamClass.
Please see stack trace in the comments part
###@###.### 2004-09-20
###@###.### 2004-09-20
Comments
SUGGESTED FIX
A fix has been provided to the sustaining engineering. Though this should fix this problem, there may be performance degradations due to this fix. It is better to sacrifice performance for correctness. In the future, we plan to rewrite the ObjectStreamClass implementation to be more robust.
###@###.### 10/8/04 22:16 GMT
08-10-2004
CONVERTED DATA
BugTraq+ Release Management Values
COMMIT TO FIX:
dragon
29-09-2004
EVALUATION
There is a deadlock here which seems to occur relatively rarely. There is
a simple but inefficient fix that introduces lock contention on a single
shared lock. We need to fix this more carefully in several places.
For now I'll commit this to a later Tiger update release.
29-09-2004
WORK AROUND
As far as we know, there is no workaround
###@###.### 2004-09-20