NaughtyYang opened a new issue, #11769:
URL: https://github.com/apache/seatunnel/issues/11769

   ### Search before asking
   
   - [x] I had searched in the 
[issues](https://github.com/apache/seatunnel/issues?q=is%3Aissue+label%3A%22bug%22)
 and found no similar issues.
   
   
   ### What happened
   
   
Mysql-CDC模式,sink端也是mysql,STREAMING模式,运行一段时间后,就报这个错,应该是连接失效了,但是seatunnel还是用了这个连接,没有探活等机制
   
   ### SeaTunnel Version
   
   2.3.12
   
   ### SeaTunnel Config
   
   ```conf
   sink {
     jdbc {
         url = 
"jdbc:mysql://localhost:3306/a?useSSL=false&serverTimezone=Asia/Shanghai"
         driver = "com.mysql.cj.jdbc.Driver"
         user = "xx"
         password = "xx"
          max_retries = 5
         
         table = "${table_name}"
         generate_sink_sql = true
          
          connection_check_timeout_sec = 1800
          properties {
                connection-test-query = "select 1"
                validation-timeout = 3000
                max-lifetime = 600000
                leak-detection-threshold = 60000
          }
         
         database = a
         
         primary_keys = ["${primary_key}"]
         
         
     }
   }
   ```
   
   ### Running Command
   
   ```shell
   ./seatunnel.sh --config ../config/a.conf
   ```
   
   ### Error Exception
   
   ```log
   Caused by: java.sql.SQLException:No operations allowed after statement closed
   ```
   
   ### Zeta or Flink or Spark Version
   
   _No response_
   
   ### Java or Scala Version
   
   _No response_
   
   ### Screenshots
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to