[omniORB] occasional Exception "giopStream::CommFailure from giopStream.cc:878(0, MAYBE, COMM_FAILURE_WaitingForReply)"

Duncan Grisby duncan at grisby.org
Tue Oct 13 12:14:20 BST 2009


On Saturday 10 October, Peter Klotz wrote:

[...]
> > the network between client and server seems no problem (ping and it's alive)
> > can someone give me some clues to locate the problem?
> 
> I am seeing the same problem after upgrading to omniORB 4.1.4. It
> never occurred in 4.1.3.

Strange. I don't think any of the changes between 4.1.3 and 4.1.4 can
have caused that. The only changes to anything in the transport layer
are to do with connection establishment. Nothing has changed in the code
that manages a connection once it's open.

It would be helpful if you or Isaac could get a trace from traceLevel 30
from both the client and server when it happens. Please run with
traceTime 1 traceThreadId 1 so it's possible to correlate things between
the two ends.

Cheers,

Duncan.

-- 
 -- Duncan Grisby         --
  -- duncan at grisby.org     --
   -- http://www.grisby.org --



More information about the omniORB-list mailing list