[#CORE-1763] The client library does not set options SO_KEEPALIVE, TCP_NODELAY for socket at connection

Firebird Core

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

Created: 26/Feb/08 01:45 AM Updated: 30/May/11 09:51 AM

Component/s:

API / Client Library

Affects Version/s:

2.1 RC1

Fix Version/s:

2.5 Alpha 1

Time Tracking:

Not Specified

Issue Links:

Relate

This issue relate to:

~~CORE-3387~~ Client library could hang infinitely waiting for a reply packet on a forcibly disconnected server socket

Planning Status:

Unspecified

Description

« Hide

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

All

Comments

Work Log

Change History

Version Control

Subversion Commits

Sort Order:

[ Permalink | « Hide ]

Alexander Peshkov added a comment - 26/Feb/08 03:25 AM

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.

[ Permalink | « Hide ]

Vlad Khorsun added a comment - 21/Mar/08 11:43 AM

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