From: Scott M Stark <scott.stark@jb...> - 2005-11-28 18:05:50
In working with the jrockit runtime analyzer I ran across this
description of the types of lock optimization jrockit attempts:
One quote from it that I don't quite understand:
"A special note regarding locks: if wait/notify/notifyAll is called on a
lock, it will automatically inflate to a fat lock. A good advice (not
only for this reason) is therefore not to mix actual locking with this
kind of notification on a single object."
Since any wait/notify/notifyAll construct requires acquiring the target
object monitor, I guess they are saying that use of such an object
monitor in locking schemes in addition to the notification usage is
going to result in a contended fat lock?
Chief Technology Officer