[omniORB] COMM_FAILURE in CosNaming::NamingContext::_narrow
Duncan Grisby
duncan at grisby.org
Mon May 12 18:02:02 BST 2003
On Friday 9 May, "Qian Feng" wrote:
> And here is the trace information when it failed with
> traceLevel set to 40:
[...]
> 4749 4f50 0100 0100 5800 0000 0000 0000 GIOP....X.......
[...]
> omniORB: inputMessage: from giop:tcp:10.1.1.13:2809 12 bytes
> omniORB:
> 4749 4f50 0102 0105 0000 0000 GIOP........
> omniORB: To endpoint: giop:tcp:10.1.1.13:2809. Send GIOP 1.0
> MessageError because a protocol error has been detected. Connection is
> closed.
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.
Cheers,
Duncan.
--
-- Duncan Grisby --
-- duncan at grisby.org --
-- http://www.grisby.org --
More information about the omniORB-list
mailing list