[FireDAC] [Phys] [MySQL] MySQL server has gone away

[FireDAC] [Phys]  [MySQL] MySQL server has gone away

Reason:

MySQL and other databases, which are essentially the socket server.

As a network communication service, there is a mechanism-the regular active kick off the long-inactive socket client connection, timed kicking off the zombie connection, the service side to maintain stability and efficient service.

ORACLE, MYSQL, MSSQL ... Other long-connected socket services have such a mechanism, which is a common practice.

MySQL server has gone away--tell the client that I (MySQL database) has kicked you off.

Workaround:

1) in the MySQL database side settings, this allows the "Manger not pull Cheung" time to set a bit longer.

2) in the database middleware connection pool will exceed the specified time of the connection, automatically reconnect the database.

[FireDAC] [Phys] [MySQL] MySQL server has gone away