You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I update this package version to d0a5481, it alway show follow error log. After a simple investigation, I think there should using SyscallConn.Control instead of SyscallConn.Read in connCheck. If there is no data in the socket, we maybe got a reading-timeout error when driver do a connection liveness checking by using SyscallConn.Read. @vmg , do you think so? Thanks.
Issue description
Tell us what should happen and what happens instead
#934
When I update this package version to d0a5481, it alway show follow error log. After a simple investigation, I think there should using
SyscallConn.Control
instead ofSyscallConn.Read
inconnCheck
. If there is no data in the socket, we maybe got a reading-timeout error when driver do a connection liveness checking by usingSyscallConn.Read
. @vmg , do you think so? Thanks.Example code
Error log
the package always logging:
Configuration
Driver version (or git SHA):
d0a5481
Go version:
go1.12.4
Server version:
MySQL 5.5.31
Server OS:
Centos 7.0
The text was updated successfully, but these errors were encountered: