[omniORB] COMM_FAILURE in CosNaming::NamingContext::_narrow

[Qian Feng]

Yes, the names server is omniNames. But, with -ORBtraceLevel 40,  I
didn't see any trace info at the mean time when the exception happen on
the client, the only trace message I can see is:
...
omniORB: Scan for idle connections done (1052789441,420163000).
omniORB: Scan for idle connections (1052789446,430205000)
omniORB: Scavenger reduce idle count for strand 0x404004c0 to 8
omniORB: Scan for idle connections done (1052789446,430205000).
omniORB: Scan for idle connections (1052789451,440125000)
omniORB: Scavenger reduce idle count for strand 0x404004c0 to 7
...

But it does have the following trace information when _narrow runs
successfully:

omniORB: inputMessage: from giop:tcp:10.1.1.125:4151 100 bytes
omniORB: 
4749 4f50 0100 0100 5800 0000 0000 0000 GIOP....X.......
1a00 0000 01cd cdcd 0b00 0000 4e61 6d65 ............Name
5365 7276 6963 65cd 0600 0000 5f69 735f Service....._is_
6100 6500 0000 0000 2800 0000 4944 4c3a a.e.....(...IDL:
6f6d 672e 6f72 672f 436f 734e 616d 696e omg.org/CosNamin
672f 4e61 6d69 6e67 436f 6e74 6578 743a g/NamingContext:
312e 3000                               1.0.
omniORB: sendChunk: to giop:tcp:10.1.1.125:4151 25 bytes
omniORB: 
4749 4f50 0100 0101 0d00 0000 0000 0000 GIOP............
1a00 0000 0000 0000 01                  .........


And how can I change the client to make it send a specified GIOP version
message?

Thanks,
Qian Feng

-----Original Message-----
From: Duncan Grisby [mailto:duncan at grisby.org] 
Sent: Tuesday, May 13, 2003 12:02 AM
To: Qian Feng
Cc: omniorb-list at omniorb-support.com
Subject: Re: [omniORB] COMM_FAILURE in CosNaming::NamingContext::_narrow


The client sent a GIOP 1.0 request, and got a GIOP 1.2 reply, so it
correctly threw an exception. Is the name server omniNames?  If so,
please run it with -ORBtraceLevel 40 and post the trace. If it's someone
else's name service, complain to them that they're replying to messages
with the wrong GIOP version.