Orbix 2.2C01 [on NT] interoperability with VisiBroker or omniORB2?

[Ian Brennan]

Orbix 2.3c uses LOCATE_REQUEST, LOCATE_FORWARD and LOCATE_REPLY
properly.   In fact we now depend on these messages as part of the
normal operation of Orbix.  It was part of the changes needed to use
IIOP as the default protocol.

Ian, QA IONA Technologies.


Sai-Lai Lo wrote:

[...]

> I did some investigation and find that the Orbix server fails to
response

> to a IIOP LocateRequest message which omniORB2 clients always send
> before
> the first invocation on an object.
>
> This also explains why all other clients except omniORB2 and
> VisiBroker for
> C++ can talk to the server, i.e. they do not issue IIOP LocateRequest
> messages.
>
> I should also say that the omniORB2 client can talk to the same server
> code
> running on Orbix 2.2MT for Solaris. That is, the Orbix solaris version
> does
> handle IIOP LocateRequest properly.
>
> I hope this bug in Orbix will be fixed soon.
>
> In the mean time, if you have to use omniORB2 client to talk to an
> Orbix
> server on NT, you have to patch the omniORB2 stub code to tell it not
> to
> issue IIOP LocateRequest message. Just look into the *SK.cc files and
> comment out the line:
>
>   assertObjectExistent();
>
> Regards,
>
> Sai-Lai Lo
>
> --
> E-mail:         S.Lo@orl.co.uk          |       Olivetti & Oracle
> Research Lab
>                                         |       24a Trumpington Street
>
> Tel:            +44 223 343000          |       Cambridge CB2 1QA
> Fax:            +44 223 313542          |       ENGLAND