[omniORB] omniORBpy lock-up
Duncan Grisby
dgrisby@uk.research.att.com
Mon, 09 Jul 2001 15:33:00 +0100
On Sunday 8 July, "Eric C. Newton" wrote:
[...]
> Sometimes there's a KeyError exception between the thr_acq and the
> thr_rel. Shortly after this occurs, my server locks up because the
> lock is never released.
>
> I changed the code to:
[...]
> This only releases the lock and prints the error. I'm not really sure
> what's going on. Never happens under Linux (RedHat 7.1) on the same
> machine, but happens frequently on WindowsME.
How odd. What traceback do you get? I think it's a good idea to add
the try..finally for robustness, but I think that's just masking a
more serious problem. Something somewhere has become confused about a
thread's thread id.
Is anyone successfully running omniORBpy on Windows ME?
Cheers,
Duncan.
--
-- Duncan Grisby \ Research Engineer --
-- AT&T Laboratories Cambridge --
-- http://www.uk.research.att.com/~dpg1 --