The client library does not set options SO_KEEPALIVE, TCP_NODELAY for socket at connection [CORE1763]

[firebird-automations]

Submitted by: John Kilin (johnkilin)

Relate to CORE3387

The client library does not set options SO_KEEPALIVE, TCP_NODELAY for socket at connection

Commits: 5cb43d8

[firebird-automations]

Modified by: @AlexPeshkoff

assignee: Alexander Peshkov [ alexpeshkoff ]

[firebird-automations]

Commented by: @AlexPeshkoff

SO_KEEPALIVE is needed for server to watch lost clients. How do you imagine client watching for lost server?
What about TCP_NODELAY... I'm not sure, does this option missing at client breaks something in connectivity algorithm. Can you provide a sample? If needed, I can turn it on easily.

[firebird-automations]

Modified by: @hvlad

assignee: Alexander Peshkov [ alexpeshkoff ] => Vlad Khorsun [ hvlad ]

[firebird-automations]

Commented by: @hvlad

Client socket for database connection now set TCP_NODELAY option (accordingly to firebird.conf setting, by default on).
Client socket for evens processing now set SO_KEEPALIVE option

[firebird-automations]

Modified by: @hvlad

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

Fix Version: 2.5 Alpha 1 [ 10224 ]

[firebird-automations]

Modified by: @pcisar

status: Resolved [ 5 ] => Closed [ 6 ]

[firebird-automations]

Modified by: @dyemanov

Link: This issue relate to CORE3387 [ CORE3387 ]

[firebird-automations]

Modified by: @pavel-zotov

QA Status: No test

[firebird-automations]

Modified by: @pavel-zotov

status: Closed [ 6 ] => Closed [ 6 ]

QA Status: No test => Cannot be tested