AW: [omniORB] omniNames + bidir = Detected GIOP 1.2 protocol error ininput message

[Barthel Marco (MPA/DS)]

Hi,

I don't know if this is a bug or if it was intended.

We had the same problem. A solution to this problem is the following:

Either copy the ROOT-Context-IOR from the omninames console window and use it

or

provide the right GIOP-Version (1.2) when using

-ORBInitRef NameService=corbaname::1.2@<your-omninames-hostname

on the commandline.

Hope that helps.

-marco

> -----Ursprüngliche Nachricht-----
> Von: omniorb-list-bounces at omniorb-support.com
> [mailto:omniorb-list-bounces at omniorb-support.com]Im Auftrag von Scott
> Robertson
> Gesendet: Dienstag, 27. April 2004 23:44
> An: omniORB List
> Betreff: [omniORB] omniNames + bidir = Detected GIOP 1.2 
> protocol error
> ininput message
> 
> 
> I'm working with the latest copy of omniORB from CVS. The one that has
> the fix so that python can use BiDirectional IOP. And it now does
> bidirectional calls  with a simple example. However, if I add the
> settings to my real program, my client gets the following error from
> omniNames
> 
> omniORB: From endpoint: giop:tcp:192.168.0.80:49000. Detected GIOP 1.2
> protocol error in input message
> 
> If I disable bidir support by changing the client's transport rule to 
> clientTransportRule = * unix,tcp
> 
> I don't have a problem, but if I turn it on I do.
> 
> I tried setting the serverTransportRule in /etc/omniORB.cfg to see if
> that had any effect, but I get the same result.
> 
> Anyone else run into this? Or is it due to python again?
> 
> 
> _______________________________________________
> omniORB-list mailing list
> omniORB-list at omniorb-support.com
> http://www.omniorb-support.com/mailman/listinfo/omniorb-list
>