Build the holes that SSH has entered.

Add the relevant jar package, finish writing the configuration file, finish writing the test class, run the prompt

warn:establishing SSL connection without server ' s identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must is established by default if explicit Opti On isn ' t set. For compliance with existing applications not using SSL, the Verifyservercertificate property was set to ' false '.  You need either to explicitly disable SSL by setting usessl=false, or set usessl=true for server Certificate Verification

This is because the Jdbcurl configuration is changed to

Jdbcurl=jdbc:mysql://localhost:3306/gss?useunicode=true&characterencoding=utf8&usessl= True

Continue to run the following error:

Org.hibernate.exception.GenericJDBCException:Cannot Open connectioncaused by:java.sql.SQLException: Connections couldnot being acquired from the underlying database! caused By:com.mchange.v2.resourcepool.cannotacquireresourceexception:a Resourcepool could not acquire A resource From its primary factory or source.

most of the online solutions are Check that the database connection driver user name password is properly attached to my configuration:

Jdbcurl=jdbc:mysql://localhost:3306/gss?useunicode=true&characterencoding=utf8&usessl= Truedriverclass=com.mysql.jdbc.Driveruser=Rootpassword=rootinitialpoolsize=10 maxpoolsize=30

Still reported the above error, N hours found is the MySQL driver jar package problem, with the 6.0.2, replaced by 5.1.32 can be

    <dependency>      <groupId>mysql</groupId>      <artifactid>mysql-connector-java</ artifactid>      <version>5.1.32</version>    </dependency>

Resolve failed to load class "Org.slf4j.impl.StaticLoggerBinder"

class "Org.slf4j.impl.StaticLoggerBinder". Slf4j:see http://

The solution to the official web site is that this error was reported when the Org.slf4j.impl.StaticLoggerBinder class could wasn't being loaded into memory . This happens when no appropriate slf4j binding could is found on the class path. Placing one (and only one) of Slf4j-nop.jar, Slf4j-simple.jar, Slf4j-log4j12.jar, Slf4j-jdk14.jar or Logback-classic.jar o n the class path should solve the problem. In fact, add a package called Slf4j-log4j12-1.5.11.jar to convert it, pay attention to the version number.

Build the holes that SSH has entered.