View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006958 | SymmetricDS | Bug | public | 2025-06-19 02:03 | 2025-06-19 20:06 |
| Reporter | fazri | Assigned To | |||
| Priority | high | ||||
| Status | closed | Resolution | no change required | ||
| Product Version | 3.15.12 | ||||
| Summary | 0006958: Issues with SQL Exceptions and SocketTimeout in Engine "dbMysql" (Error 600) | ||||
| Description | We are encountering intermittent errors on our "dbMysql" engine while database synchronization is actively in progress. These errors appear unexpectedly and consistently occur every 2–3 hours. Below are the configuration details, error logs, and our observations regarding the issue. | ||||
| Steps To Reproduce | Problem: The "dbMysql" engine consistently encounters periodic errors—specifically SQL exceptions and socket timeouts (e.g., java.net.SocketTimeoutException: Read timed out). These errors occur unexpectedly while database synchronization is underway, disrupting both pull and push operations, as well as tasks like the Initial Load Extract and Push jobs. Occurrence Pattern: The errors tend to appear suddenly during an active synchronization process and reoccur approximately every 2 to 3 hours. Impact: As we run multiple engines within a single instance, our current management setup (using sym_service) does not allow us to restart one engine individually without affecting the others. A full instance restart is not ideal because it causes unnecessary reconnections and added overhead on the other engines, especially given our large-scale dataset. Attempts and Considerations: - We have already reviewed our configuration settings. - The issue appears to be related to connection handling during heavy synchronization load, potentially exacerbated by long-running queries or resource contention. - We have considered adjusting JDBC parameters (e.g., adding autoReconnect=true or modifying timeout settings) to improve connection stability. | ||||
| Additional Information | 2025-06-19 04:45:49,249 ERROR [dbMysql] [SymmetricServlet] [qtp149526537-8347] Error while processing GET request for node: 001 at 127.0.0.1 with path: /dbMysql/pull StackTraceKey [SqlException:2522107566] 2025-06-19 04:46:19,252 ERROR [dbMysql] [InitialLoadExtractorJob] [dbMysql-job-8] Exception while executing job 'Initial Load Extract' StackTraceKey [SqlException:1805095580] 2025-06-19 04:46:48,349 WARN [dbPsql] [PushService] [dbpsql-push-default-476] Could not communicate with corp:000:000 at http://localhost:31415/sync/dbMysql because exception org.jumpmind.exception.IoException: java.net.SocketTimeoutException: Read timed out 2025-06-19 04:46:49,259 ERROR [dbMysql] [SymmetricServlet] [qtp149526537-27] Error while processing HEAD request for node: 001 at 127.0.0.1 with path: /dbMysql/push StackTraceKey [SqlException:2522107566] 2025-06-19 04:47:19,208 ERROR [dbPsql] [DataLoaderService] [dbpsql-pull-default-450] Failed to process incoming batch from node '000' StackTraceKey [SocketTimeoutException:2298671659] 2025-06-19 04:47:19,262 ERROR [dbMysql] [SymmetricServlet] [qtp149526537-26484] Error while processing GET request for node: 001 at 127.0.0.1 with path: /dbMysql/pull StackTraceKey [SqlException:2522107566] 2025-06-19 04:47:49,265 ERROR [dbMysql] [PushJob] [dbMysql-job-17] Exception while executing job 'Push' StackTraceKey [SqlException:1805095580] 2025-06-19 04:48:19,267 ERROR [dbMysql] [SymmetricServlet] [qtp149526537-36578] Error while processing GET request for node: 001 at 127.0.0.1 with path: /dbMysql/pull StackTraceKey [SqlException:2522107566] | ||||
| Tags | No tags attached. | ||||
|
|
This is an environmental issue. The dbMysql database appears to be slow and is timing out. Consider reducing the max batch to send on your channels. To get professional help with this issue, consider switching to SymmetricDS Pro. Here's a link to the SymmetricDS website, which describes the differences between open-source and pro: https://symmetricds.org/editions/ |