[omniORB] giopRendezvouser exit on error

[Duncan Grisby]

On Thursday 21 February, "Vinouse, Jean-Pierre \(Jean-Pierre\)" wrote:

> The client behaves in a different way as the previous one, it does not
> use the GIOP 1.2 message close connection to release the connection.
> Instead as shown by an ethereal trace the TCP connection is released
> "hardly" at TCP level (FIN packet) a few msecs after the GIOP reply has
> been sent out. I presume this cause the giopStream to throw the
> exception COMM_FAILURE_UnMarshalArguments. And it seems that in some
> circumstances (large message sent here 66kbytes, network perhaps
> degraded or slow) the SocketCollection::select() may return an error of
> type "invalid file descriptor". Following the giopRrendezvouser
> terminates and no further incoming connection can be accepted. Our
> application then triggers a reboot.
> 
> Is it an known issue ? Would a fix exists for 4.0.7 version, we could
> test it in our env.  

Are you able to try omniORB 4.1.2?  Failing that, please try the latest
snapshot on the omni4_0_develop branch:

  http://omniorb.sourceforge.net/snapshots/omniORB-4.0-latest.tar.gz

I believe the bug you are seeing has already been fixed.

Cheers,

Duncan.

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