[omniORB] WinNT TCP connection problems

[Duncan Grisby]

On Wednesday 25 February, "Clarke Brunt" wrote:

> omniORB: Client attempt to connect to giop:tcp:172.19.50.28:2179
> omniORB: Client opened connection to giop:tcp:255.255.255.255:65535

[...]
> So the first case is the connect() call failing, and the latter 2 believe
> that they have connected to 255.255.255.255:65535 but then fail to send
> (perhaps not surprisingly). In all cases, an immediate retry works. In fact
> the third case was trying to make a connection to localhost, though using
> its proper address (172.19.50.28:2179).

I'm pretty certain that the problem must be with your OS, not with
omniORB. The code that's attempting the connection just does a
connect() call, then tries to do getpeername() on the resulting
socket. If getpeername() fails, it sets the address to
255.255.255.255:65535. My guess is that the machine is overloaded,
meaning that sometimes connect() fails, and other times it partly
succeeds, but doesn't quite get it right.

You might want to instrument the code in tcpConnection.cc that calls
getpeername() to see what the errno value is when it fails.

Cheers,

Duncan.

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