[omniORB] problem using naming service with bidir transport

[Harri Pasanen]

Forgot to mention that this is OmniORB 4.0.3, omniNames running on 
Linux (Mandrake 10), as well as my client app.  I believe I've seen 
these occasional client errors also on Windows, but I cannot confirm 
at the moment.

This has the symptoms of a some sort of race condition.

After a few attempts I managed to capture a -ORBtraceLevel 40 output 
of a failing connection, a snippet of which below.

omniORB: Creating ref to remote: key<0x4e616d6553657276696365>
 target id      : IDL:omg.org/CosNaming/NamingContext:1.0
 most derived id:
omniORB: sendChunk: to giop:tcp:172.24.16.82:2809 81 bytes
omniORB:
4749 4f50 0100 0100 4500 0000 0000 0000 GIOP....E.......
0400 0000 0101 86a7 0b00 0000 4e61 6d65 ............Name
5365 7276 6963 6500 0800 0000 7265 736f Service.....reso
6c76 6500 0000 0000 0100 0000 0c00 0000 lve.............
6669 6e61 6e63 652d 6b69 7400 0100 0000 finance-kit.....
00                                      .
omniORB: inputMessage: from giop:tcp:172.24.16.82:2809 288 bytes
omniORB:
4749 4f50 0100 0101 1401 0000 0000 0000 GIOP............
0400 0000 0000 0000 2b00 0000 4944 4c3a ........+...IDL:
6f6d 672e 6f72 672f 436f 734e 616d 696e omg.org/CosNamin
672f 4e61 6d69 6e67 436f 6e74 6578 7445 g/NamingContextE
7874 3a31 2e30 002d 0100 0000 0000 0000 xt:1.0.-........
cc00 0000 0101 0200 0d00 0000 3137 322e ............172.
3234 2e31 362e 3832 0000 adc2 0600 0000 24.16.82........
ff00 0000 0000 0000 0400 0000 0000 0000 ................
0800 0000 0100 0000 0054 5441 0100 0000 .........TTA....
1c00 0000 0100 0000 0100 0100 0100 0000 ................
0100 0105 0901 0100 0100 0000 0901 0100 ................
0300 0000 1800 0000 0100 0000 0d00 0000 ................
3137 322e 3234 2e31 362e 3832 0000 f90a 172.24.16.82....
0254 5441 4800 0000 0100 0000 1800 0000 .TTAH...........
6c61 6273 2d66 6b31 2e63 6f72 702e 7472 labs-fk1.corp.tr
656d 612e 636f 6d00 2400 0000 2f74 6d70 ema.com.$.../tmp
2f6f 6d6e 692d 726f 6f74 2f30 3030 3030 /omni-root/00000
3433 3130 2d31 3038 3838 3931 3436 3700 4310-1088891467.
omniORB: From endpoint: giop:tcp:172.24.16.82:2809. Detected GIOP 1.2 
protocol error in input message. Connection is closed.
omniORB: throw giopStream::CommFailure from giopImpl12.cc:1246
(0,NO,COMM_FAILURE_UnMarshalArguments)
omniORB: Client connection refcount = 1
omniORB: throw giopStream::CommFailure from giopStream.cc:796
(0,MAYBE,COMM_FAILURE_WaitingForReply)
omniORB: Client connection refcount = 0
omniORB: Client close connection to giop:tcp:172.24.16.82:2809
omniORB: throw COMM_FAILURE from omniObjRef.cc:754 
(MAYBE,COMM_FAILURE_WaitingForReply)
Caught system exception COMM_FAILURE,
unable to contact the naming service.: Unknown error 1096024071



On Friday 17 September 2004 11:04, Harri Pasanen wrote:
> Hi,
>
> I haven't yet looked in detail what is causing this, but if I had
>
> clientTransportRule = 192.168.1.127/255.255.255.0		bidir,tcp
>
> and omniNames running at 192.168.1.127
>
> In my application I'm getting occasionally, but not systematically:
>
> Caught system exception COMM_FAILURE,
> unable to contact the naming service.: Unknown error 1096024071
>
> Looks like by removing the bidir policy from the rule, it never
> fails.
>
> My app's POA has the bidir policy set.
>
> nameclt never fails, no matter what the rule policy is.   But I
> suspect nameclt's  POA does not implement the bidir policy.
>
> Does this ring any  bells for anyone, or should I look further?
>
> Harri
>


This message, including any attachments, is intended only for the person(s) to whom it is addressed. If you received it in error, please let us know and delete the message from your system. This message may be confidential and may fall under the duty of non-disclosure. Any use by others than the intended addressee is prohibited. Trema shall not be liable for any damage related to the electronic transmission of this message, such as failure or delay of its delivery, interception or manipulation by third parties, or transmission of viruses or other malicious code.