If I recall correctly, the owner is only set when someone successfully acquires a write lock, as multiple readers are possible concurrently, and as such any one of them cannot be the owner. Most likely either another thread has it, or one of the two read waiters tried to grab a read lock again recursively after 351 requested its write lock. I'm not sure if the latter is actually a problem that can happen though. Regards, Rene On Thu, Apr 9, 2009 at 8:43 PM, David McPaul <dlmcpaul@xxxxxxxxx> wrote: > I can only assume that the rwlock is not owned by anyone but the 3 > threads are waiting on it to be released? > > -- > Cheers > David >