Yonik Seeley wrote:
I ran across a situation where a great number of threads were blocked on ensureIndexIsRead(), even after it had already been loaded.
That sounds bizarre. A sync block that tests a field for non-null shouldn't tie things up much, I wouldn't think. Are you sure that one of the threads wasn't actually reading the index? Or perhaps some other method also synchronizes on the same object?
Doug --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]