6.9.7. Connector Logging Configuration
The connector is able to modify what is logged using different configuration
Informational messages like those below indicate that a client-side session
did not properly close connection to the connector using a regular mysql
WARN [MySQLBridge] - [10.3.1.240:35686] C>S ended. S>C streaming did not finish within
bridgeServerToClientForcedCloseTimeout=500 (ms). Will be closed anyway !
INFO [MySQLBridge] - [10.3.1.240:35686] Server>Client thread didn't finish cleanly - return code was: 1
Load balancers (especially physical ones) tend to do this when testing the
connector, so these messages are expected when behind a load-balancer. Since
the same error could come from buggy application code, the default is to log
If you know where the disconnects are coming from, you can safely disable
this feature by setting the tpm option
--connector-disable-connection-warnings (in [Tungsten Clustering for MySQL 5.0 Manual]) to
./tools/tpm configure alpha --connector-disable-connection-warnings=true
Updating these values require a connector restart (via tpm update) for the
changes to be recognized.