@@ -215,14 +215,13 @@ Socket timeouts are generated when the database server stops responding to reque
- Your database server, or the machine running it, may have been temporarily shut down for maintenance purposes, or is in the process of rebooting.
- Your database server may be resource-starved (CPU or disk I/O bound), either due to a background process (such as a backup task) or due to an intensive database query from any source.
- There could be a hardware failure at any point between the client and the server causing a disrupted network connection or other type of fault. For example, a router may be rebooting once or twice per day under specific loads due to age-related electrical faults. To rule out network failure, one must run a long-term ping test from the client to the server or vice versa - the amount of packets lost should ideally be zero.
- There could be a hardware failure at any point between the client and the server causing a disrupted network connection (packet loss) or other type of fault. For example, a router may be rebooting once or twice per day under specific loads due to age-related electrical faults. To rule out network failure, one must run a long-term ping test from the client to the server or vice versa - the amount of packets lost should ideally be zero.
- There could be a firewall (on the database server side) that is configured to block connections via timeout when a single IP address makes too many connection attempts within a given time period, or reaches a connection limit.
**Why does LiteBans give socket timeout errors while other plugins do not?** LiteBans sets an attribute called a socket timeout (Not to be confused with "connection timeout", which specifically refers to the timeout used while attempting to create a new connection.) - for connection pools like HikariCP, the default socket timeout is infinite unless specified via the `socketTimeout` connection property. The socket timeout defines the maximum amount of time that will be spent waiting for an active query to finish and receive a response from the database server. Clients which have an infinite socket timeout will simply hang indefinitely while awaiting a response, which will produce no visible error messages while tasks have all frozen up internally.
**Why does LiteBans give socket timeout errors while other plugins do not?** LiteBans sets an attribute called a socket timeout (Not to be confused with "connection timeout", which specifically refers to the timeout used while attempting to create a new connection.) - for connection pools like HikariCP, the default socket timeout is infinite unless specified via the `socketTimeout` connection property. The socket timeout defines the maximum amount of time that will be spent waiting for an active query to finish and receive a response from the database server. Clients which have an infinite socket timeout will simply hang indefinitely while awaiting a response, which will produce no visible error messages while tasks have all frozen up.
For LiteBans specifically, the socket timeout is set to the same value as the connection timeout - 25 seconds by default. Other plugins typically leave it unset or set a different value.
For LiteBans specifically, the socket timeout is set to the same value as the connection timeout - 25 seconds by default.
### Connection ... marked as broken because of ... Read timed out
### Connection ... marked as broken because of SQLSTATE(08S01) ... Read timed out
### No operations allowed after connection closed:
