apiConnect does not respect timeouts

Description

createConnectionTo calls findRemoteEndpoint and findRemoteEndpoint may block indefinitely waiting for network operations to complete.

This call should happen under a timeout call so connect terminates when it blocks for too long.

Actually, only the Network.Socket.connect call happens under a timeout call. An almost immediately following recvInt32 call can block indefinitely too.

Environment

None

Activity

Show:
Facundo Dominguez
May 21, 2015, 4:57 PM

There is a timeout provided per-connection.

And there is a transport-wide connection timeout in an open PR. The per-connection timeout overrides the transport-wide timeout.

Tim Watson
May 21, 2015, 2:58 PM

How do we decide on the policy that governs the timeout duration?

Assignee

Tim Watson

Reporter

Facundo Dominguez

Labels

None

External issue ID

None

OS

Linux

Affects versions

Priority

Major