Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support ER_CLIENT_INTERACTION_TIMEOUT #970

Closed
bgrainger opened this issue Apr 21, 2021 · 4 comments
Closed

Support ER_CLIENT_INTERACTION_TIMEOUT #970

bgrainger opened this issue Apr 21, 2021 · 4 comments

Comments

@bgrainger
Copy link
Member

In MySQL 8.0.24

Previously, if a client did not use the connection to the server within the period specified by the wait_timeout system variable and the server closed the connection, the client received no notification of the reason. Typically, the client would see 1Lost connection to MySQL server during query1 (CR_SERVER_LOST) or 1MySQL server has gone away1 (CR_SERVER_GONE_ERROR).

In such cases, the server now writes the reason to the connection before closing it, and client receives a more informative error message, The client was disconnected by the server because of inactivity. See wait_timeout and interactive_timeout for configuring this behavior. (ER_CLIENT_INTERACTION_TIMEOUT).

We need to handle the Error payload sent by MySQL Server (containing this error message) before it closes the connection.

@bgrainger
Copy link
Member Author

Fixed in 1.3.4.

@olx
Copy link

olx commented Jun 14, 2022

the same problem in version 2.1+ (mysql server 8.0.26) with EF (Pomelo provider)

@bgrainger
Copy link
Member Author

the same problem in version 2.1+ (mysql server 8.0.26) with EF (Pomelo provider)

Please create a new issue with full details of the problem.

@mguinness
Copy link
Contributor

the same problem in version 2.1+ (mysql server 8.0.26) with EF (Pomelo provider)

Also cross posted at PomeloFoundation/Pomelo.EntityFrameworkCore.MySql#1545 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants