[omniORB] Bidir & SSL trouble

[Vladimir Panov]

I tried running my BiDir+SSL examples with your options, and found out 
the same problem. The examples are OK if I start the client without the 
"endPoint" option.


Slava Garelin wrote:

>In case adding SSL support in bidir example, callback-s not going.
>
>server command-line :
>
>bd_server -ORBtraceLevel 25   -ORBofferBiDirectionalGIOP 1 
>-ORBacceptBiDirectionalGIOP 1 -ORBclientTransportRule "* bidir,ssl,tcp" 
>-ORBserverTransportRule "* bidir,ssl,tcp" -ORBendPoint 
>"giop:ssl:192.168.100.10:9998"  -ORBverifyObjectExistsAndType 0 
>-ORBoneCallPerConnection 0
>============
>
>client command-line :
>
>bd_client IOR:0100.......000e27 1 4 -ORBtraceLevel 25   
>-ORBofferBiDirectionalGIOP 1 -ORBacceptBiDirectionalGIOP 1 
>-ORBclientTransportRule "* bidir,ssl,tcp" -ORBserverTransportRule "* 
>bidir,ssl,tcp" -ORBendPoint "giop:ssl:192.168.100.10:9999"  
>-ORBverifyObjectExistsAndType 0 -ORBoneCallPerConnection 0
>============
>
>server output :
>omniORB: Server accepted connection from giop:ssl:192.168.100.10:60865
>omniORB: giopWorker task execute.
>omniORB: Accepted connection from giop:ssl:192.168.100.10:60865 because of 
>this 
>rule: "* bidir,ssl,tcp"
>omniORB: inputMessage: from giop:ssl:192.168.100.10:60865 314 bytes
>omniORB:  recieve codeset service context and set TCS to (ISO-8859-1,UTF-16)
>omniORB:  receive bidir IIOP service context: (192.168.100.10:9999 )
>omniORB: Accepted request from giop:ssl:192.168.100.10:60865 to switch to 
>bidire
>ctional because of this rule: "* bidir,ssl,tcp"
>omniORB: Creating ref to remote: root/bidir<0>
> target id      : IDL:cb/CallBack:1.0
> most derived id: IDL:cb/CallBack:1.0
>bd_server: Starting a new worker thread
>omniORB: sendChunk: to giop:ssl:192.168.100.10:60865 24 bytes
>omniORB: throw giopStream::CommFailure from 
>giopStream.cc:1045(0,NO,TRANSIENT_Co
>nnectFailed)
>omniORB: throw TRANSIENT from omniObjRef.cc:732 (NO,TRANSIENT_ConnectFailed)
>cb_server: Lost a client!
>cb_server: Worker thread is exiting.
>===============
>
>If client endpoint is ":tcp:" then all works well.
>
>  
>