[omniORB] interoperability with Orbacus 4

[Randy Shoup]

Just to close the loop, it looks like this is a known bug in Orbacus
4.0.1, when responding to LocateRequest.  Later versions (e.g., 4.0.3)
have fixed it.

No problem on the omniORB side.

Duncan Grisby wrote:
> 
> On Monday 25 September, "Azariah Jeyakumar" wrote:
> 
> > It seems like omniORB interoperability with Orbacus 4 is limited.
> 
> Odd. I'm sure I've seen reports that it works fine. Maybe that's only
> with the C++ version of Orbacus.
> 
> > I stepped through the omniorb client stub code and found out that the
> > message size in the reply of the LocateRequest is -4 which, as an unsigned
> > number, is bigger that the MaxMessageSize acceptable to the omniorb client
> > and I get a COMM_FAILURE. Does anyone know more information about this
> > problem such as:
> 
> Please can you send the output you get when you run a simple omniORB
> client, giving it command line arguments "-ORBtraceLevel 30
> -ORBtraceInvocations". That will dump all the IIOP traffic, so we'll
> be able to see what's going on.
> 
> Cheers,
> 
> Duncan.
> 
> --
>  -- Duncan Grisby  \  Research Engineer  --
>   -- AT&T Laboratories Cambridge          --
>    -- http://www.uk.research.att.com/~dpg1 --


-- 

-- Randy
_________________________________________________________________  
Randy Shoup                                     (650)216-2038  
Senior Architect                                rshoup@tumbleweed.com  
Tumbleweed Communications Corporation