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

2004-10-08

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.