@@ -224,7 +224,7 @@ Socket timeouts are generated when the database server stops responding to reque
**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.
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 - 95 seconds by default. Other plugins typically leave it unset or set a different value.
### Connection ... marked as broken because of SQLSTATE(08S01) ... Read timed out
