[omniORB] Unexpected behaviour when running against JacORB

[Duncan Grisby]

On Thursday 7 February, Arno.Schmidmeier@sirius-eos.com wrote:

> I am using OmniORB 3.04 recompiled with MS Visual C++ SP3 against JacORB 1.4
> beta 2. 

[...]
> omniORB: LocateRequest to remote:
> key<0x5374616e64617264496d706c4e616d652f001039
> 293c1119363448>
> omniORB: strand Ripper: start.
> omniORB: scavenger : start.
> 
> <<<<
> Here I press control c
> And now I see the expected behaviour

I suspect the problem is that JacORB is not properly replying to the
LocateRequest that omniORB issues. If that is the case, it's a bug in
JacORB. You can stop omniORB from doing a LocateRequest by giving it
the argument -ORBverifyObjectExistsAndType 0, but the proper solution
is for JacORB to be fixed.

Cheers,

Duncan.

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