[omniORB] Blocking of deactivate_object in omni3

[Neil Pilgrim]

Hi all,

>From what I've read in H&V, deactivate_object is supposed to return
immediately, or at least not block until the object is destroyed.
However that's not the behaviour I see; the cpu usage goes through the
roof and it doesn't return for a 'long' time (seconds, minutes,...).

Is there some caveat to using deactivate_object, where it might not
return immediately? or should this be guaranteed by corba, ie. is it an
omni3 bug? Even if using a ServantLocator/Activator (are they the right
terms?), a bug/hold there should just stop the etherealisation, not the
deactivation, right?

Thanks,

-- 
Neil