[omniORB] Bidirectional client using normal connection because it is only GIOP 1.0

Jim Bell Jim at JC-Bell.com
Mon Nov 4 22:34:27 GMT 2019


I figured it out!

You specify the iiop version in the corbaloc URL you use to to reach the 
server.  See the CORBA-2.6.1-IIOP...  spec, section "13.6.10.1 corbaloc 
URL".

Instead of:

     corbaloc::127.0.0.1:12551/mytag

I made it this:

     corbaloc:iiop:1.2 at 127.0.0.1:12551/mytag

The bad "...using normal connection ..." messages go away, and now I'm 
getting friendly messages like these:

omniORB: (?) 2019-11-04 16:15:08.961000: Enable rope for bidirectional GIOP.
omniORB: (?) 2019-11-04 16:15:08.971000: Client registered bidirectional 
connection to giop:tcp:127.0.0.1:12551
omniORB: (?) 2019-11-04 16:15:08.974000: Send bidir IIOP service 
context: ( ...

omniORB: (5) 2019-11-04 16:15:08.998000: Receive bidir IIOP service 
context: ( ...

omniORB: (5) 2019-11-04 16:15:08.999000: Accepted request from 
giop:tcp:... to switch to bidirectional because of this rule: "* 
bidir,unix,ssl,tcp"


Here's the callback sequence now:

omniORB: (?) 2019-11-04 16:15:11.390000: sendChunk: to 
giop:tcp:127.0.0.1:12551 68 bytes
omniORB: (5) 2019-11-04 16:15:11.391000: inputMessage: from 
giop:tcp:[::ffff:127.0.0.1]:1655 68 bytes
omniORB: (5) 2019-11-04 16:15:11.391000: sendChunk: to 
giop:tcp:[::ffff:127.0.0.1]:1655 26 bytes
omniORB: (6) 2019-11-04 16:15:11.393000: inputMessage: from 
giop:tcp:127.0.0.1:12551 26 bytes
omniORB: (?) 2019-11-04 16:15:11.394000: sendChunk: to 
giop:tcp:127.0.0.1:12551 84 bytes
omniORB: (5) 2019-11-04 16:15:11.396000: inputMessage: from 
giop:tcp:[::ffff:127.0.0.1]:1655 84 bytes
omniORB: (5) 2019-11-04 16:15:11.396000: sendChunk: to 
giop:tcp:[::ffff:127.0.0.1]:1655 80 bytes
omniORB: (6) 2019-11-04 16:15:11.398000: inputMessage: from 
giop:tcp:127.0.0.1:12551 80 bytes


On 2019-11-04 1:26 PM, Jim Bell wrote:
> Hi!
>
> omniORB + omniORBpy 4.2.3  with Python 2.7.
>
> I'm trying to use bidirectional GIOP, in combination with omniINSPOA.
>
> I've carefully set it up per the docs, and calls and callbacks work, 
> but I get this message all over the place (traceLevel 25):
>
>     Bidirectional client using normal connection because it is only 
> GIOP 1.0
>
> That's a pretty definitive indicator that bidirectional isn't working, 
> right?
> ...



More information about the omniORB-list mailing list