Springboot using JPA to remove feature SQL error resolution

Source: Internet
Author: User
Tags sql error

Springboot using the JPA times error:

Only delete the Times wrong,

"Data": "Delete failed because: Could not open JPA Entitymanager for transaction; Nested exception is javax.persistence.PersistenceException: Com.mysql.jdbc.exceptions.jdbc4.CommunicationsException:Communications Link failure\n\nthe last packet successfully Received from the server was 190,731 milliseconds ago. The last packet sent successfully to the server was 4 milliseconds ago. ",
"Success": false

Solution: Added configuration: &failoverreadonly=false

For the Chinese environment, the MySQL connection URL can usually be set to:
jdbc:mysql://localhost:3306/test?user=root&password=&useunicode=true&characterencoding=gbk& Autoreconnect=true&failoverreadonly=false

In the case of using a database connection pool, it is best to set the following two parameters:
Autoreconnect=true&failoverreadonly=false

Springboot using JPA to remove feature SQL error resolution

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.