Bug #83600 MYSQL_OPT_CONNECT_TIMEOUT not fully documented

• Submitted: 28 Oct 2016 14:10
• Modified: 31 Oct 2016 9:56
• Reporter: Peter Laursen (Basic Quality Contributor)
• Status: Verified
• Category: MySQL Server: C API (client library)
• Severity: S3 (Non-critical)
• Version: any
• OS: Any
• CPU Architecture: Any

[28 Oct 2016 14:10] Peter Laursen

Description:
http://dev.mysql.com/doc/refman/5.7/en/mysql-options.html 

MYSQL_OPT_CONNECT_TIMEOUT (argument type: unsigned int *)
The connect timeout in seconds.

However I don't find it documented anywhere what the default (client-initiated) connect_timeout will become if not specified in mysql_options(). Or will the client never initiate a timeout in connection phase in such case?

How to repeat:
See above.

The background for this report is a user still on MySQL 5.0.67 who seems to expriences this https://bugs.mysql.com/bug.php?id=36225 . The bug report says it affects only Windows, but our user is running MySQL on SUSE Linux Enterprise Server 11 Patch 1.

Symptoms are same: connection times out after ~20 seconds of trying to establish connecton, no mattter how high server connect_timeout is specified.  In our client program we do not specify any MYSQL_OPT_CONNECT_TIMEOUT. 

Suggested fix:
Clarify in docs. 

I would also to know if bug36225 is fixed in 5.0.96 or not. This is not clear from discussion in above mentioned and linked bug reports, I think.

[31 Oct 2016 9:54] Chiranjeevi Battula

Hello Peter,

Thank you for the bug report.

Thanks,
Chiranjeevi.

[31 Oct 2016 9:56] Peter Laursen

As I wrote "I would also to know if bug36225 is fixed in 5.0.96 or not."