[omniORB] COMM_FAILURE_UnMarshalArgument - explanation needed

[Wernke zur Borg]

Further to my previously reported problem of an endless loop (RE: [omniORB]
Endless loop in omniORB - need help!) we observe spurious
COMM_FAILURE_UnMarshalArgument exceptions on both sides of a server-client
connection. No endless loop is entered in these cases.

This is the trace:

omniORB: (5) inputMessage: from giop:tcp:195.74.176.35:57104 12 bytes
omniORB: (5) 
4749 4f50 0102 0005 0000 0000           GIOP........
omniORB: (5) throw giopStream::CommFailure from
giopImpl12.cc:1243(0,NO,COMM_FAILURE_UnMarshalArguments)
omniORB: (5) Server connection refcount = 1
omniORB: (5) Server connection refcount = 0
omniORB: (5) Server close connection from giop:tcp:195.74.176.35:57104

In the same time interval we had this sequence with input messages several
times on both sides. In no case we found a corresponding "sendChunk" of
these 12 bytes on the other side. Where do they come from? Anyway this
message seems a bit short to me...


Another occurence of the same exception but with "sendChunk" is this:

omniORB: (3) sendChunk: to giop:tcp:195.74.176.35:57093 24 bytes
omniORB: (3) 
4749 4f50 0102 0001 0000 000c 0000 033c GIOP...........<
0000 0000 0000 0000                     ........
omniORB: (3) throw giopStream::CommFailure from
giopStream.cc:825(0,NO,COMM_FAILURE_UnMarshalArguments)
omniORB: (3) Server connection refcount = 1
omniORB: (3) Server connection refcount = 0
omniORB: (3) Server close connection from giop:tcp:195.74.176.35:57093

In this case a previous method invocation of the other side timed out. Here
I cannot see anything invalid with the message, all previous messages on the
same connection with just a different count (033a, 0338, 0336, ...) were
sent without a problem.


Could somebody perhaps explain what could be the cause for these exceptions?

Thanks in advance
---
Wernke zur Borg
VEGA Informations-Technologien GmbH
Robert-Bosch-Str. 7
64293 Darmstadt / Germany
Tel: +49-(0)6151-8257-128