[omniORB] omniOrbPOA deadlock

[Duncan Grisby]

On Monday 9 July, "Renzo Tomaselli" wrote:

>     there seems to be a deadlock in poa.cc which is due to the actual usage
> of servant_activator_lock.

I'll look into this. It does sound like a problem.

[...]
> All of this seems due to the strange identity switch of objrefs when the
> connected servant is deactivated: they switch from local to remote, so that
> next invokation goes through the normal marshalling procedure of remote
> objects and it calls back, although objref and servant are colocated.
> I feel this influences performance of servants managed by a servant
> activator, and even worse by servant locators. Beside the actual deadlock
> off course.

omniORB 4 supports fast colocated calls in all situations, so the
performance will no longer be an issue. The deadlock is probably still
a problem, though.

Cheers,

Duncan.

-- 
 -- Duncan Grisby  \  Research Engineer  --
  -- AT&T Laboratories Cambridge          --
   -- http://www.uk.research.att.com/~dpg1 --