On Mon, 10 Feb 2003, Robert Klemme wrote:

> "Elias Karakoulakis" <ek / navel.gr> schrieb im Newsbeitrag
> news:3E461257.20804 / navel.gr...
> > What's interesting is that this exception pops up in our logs:
> >
> >    Sync_m::Err::UnknownLocker: Thread(#<Thread:0x2040e560 run>) not
> locked.
> >
> > Taking a look inside sync.rb, this particular error occurs if the
> > blocking thread leaving a critical section doesn't hold the mutex/lock
> > anymore!!! Any ideas?
>
> Maybe there's an error in pairing lock acquisition and release. Maybe you
> ignored the result of a try_lock somewhere.

that's a good suggestion, the return value of try_lock has confused me before.
also you may want to see if another thread has somehow UNLOCKED the sem while
another thread had it.  note that unlock returns a value which should be
CHECKED.

-a

-- 

 ====================================
 | Ara Howard
 | NOAA Forecast Systems Laboratory
 | Information and Technology Services
 | Data Systems Group
 | R/FST 325 Broadway
 | Boulder, CO 80305-3328
 | Email: ahoward / fsl.noaa.gov
 | Phone:  303-497-7238
 | Fax:    303-497-7259
 ====================================