We've recently run into connection errors using the mysql datasource. We were told to add the autoReconnect=true parameter and if it doesn't solve our problem to adjust our mysql timeout setting on our cluster. But we're reluctant to make this type of change because it will affect all clients connecting, causing them to wait longer before their connection is timed out. Is there a mysql wait_timeout within Sisene configuration that can be tuned or is this something that will need to be addressed on the mysql server side.
Example of a connection timeout:
Build failed: BE#636134 Task not completed as expected: Table aadjustormanagers : copy_into_base_table build Error -5: Failed to read row: 0, InvalidRequestException in ETLDataReaderProto::ReadNextRow() - sessionId="32": TException - service has thrown: InvalidRequestException(why=BE#384596 The last packet successfully received from the server was 55,647 milliseconds ago. The last packet sent successfully to the server was 55,647 milliseconds ago. is longer than the server configured value of 'wait_timeout'. You should consider either expiring and/or testing connection validity before use in your application, increasing the server configured values for client timeouts, or using the Connector/J connection property 'autoReconnect=true' to avoid this problem., trace=<null>)
Please sign in to leave a comment.