这个问题有很多答案，我认为我的答案更适合另一个问题，但那个问题的答案是锁定的。它指向这个线程。

解决这个问题的方法是在application.properties中将&createDatabaseIfNotExist=true附加到spring.datasource.url字符串中。

这是非常棘手的，因为它表现为几个不同的、奇怪的、看似不相关的错误，当我试图修复它所抱怨的东西时，它只是弹出另一个错误，或者错误是不可能修复的。它抱怨无法加载JDBC，说它不在类路径中，但我以大约30种不同的方式将它添加到类路径中，并且已经是facedesking了。

如果有任何读者在访问远程服务器时遇到此问题:请确保端口是打开的

刚刚经历过。

必须做到: (这可以放在静态块初始化器中)

static{ // would have to be surrounded by try catch
    Class.forName("com.mysql.jdbc.Driver");   // this will load the class Driver
}

也可以通过以下方式获得连接:

conn = DriverManager.getConnection(DBURL,<username>,<password>);

而不是指定登录参数

  Connection conn = DriverManager.getConnection( "jdbc:mysql://localhost:3306/projects?user=user1&password=123");

的问候。

下载MySQL-JDBC-Type-4-Treiber (i.g。Mysql -connector-java-5.1.11-bin.jar从Mysql -connector-java-5.1.11.zip)

在编译和运行时期间，您需要在类路径中包含驱动程序jar。

Class.forName( "com.mysql.jdbc.Driver" ); // do this in init
// edit the jdbc url 
Connection conn = DriverManager.getConnection( "jdbc:mysql://MyDbComputerNameOrIP:3306/myDatabaseName", username, password );
Statement st = conn.createStatement();
ResultSet rs = st.executeQuery( "select * from table" );

我用一种简单的方法解决了这个问题，这对我很有用。我遇到了一些问题"com.mysql.jdbc.exceptions.jdbc4。CommunicationsException:通信链路故障”。在我的数据库里。属性文件我有这个:url:jdbc:mysql://localhost:90/myDB 只删除了端口url，导致这种方式url:jdbc:mysql://localhost/myDB，这对我来说是有效的。

如果Java试图通过SSL连接MySQL，但出现了错误，也可能发生此错误。(在我的例子中，我将Payara Server 5.193.1连接池配置为MySQL。)

有人建议设置useSSL=false。但是，由于Connector/J版本8.0.13，该设置已弃用。下面是MySQL连接器/J 8.0配置属性的摘录:

sslMode By default, network connections are SSL encrypted; this property permits secure connections to be turned off, or a different levels of security to be chosen. The following values are allowed: DISABLED - Establish unencrypted connections; PREFERRED - (default) Establish encrypted connections if the server enabled them, otherwise fall back to unencrypted connections; REQUIRED - Establish secure connections if the server enabled them, fail otherwise; VERIFY_CA - Like REQUIRED but additionally verify the server TLS certificate against the configured Certificate Authority (CA) certificates; VERIFY_IDENTITY - Like VERIFY_CA, but additionally verify that the server certificate matches the host to which the connection is attempted. This property replaced the deprecated legacy properties useSSL, requireSSL, and verifyServerCertificate, which are still accepted but translated into a value for sslMode if sslMode is not explicitly set: useSSL=false is translated to sslMode=DISABLED; {"useSSL=true", "requireSSL=false", "verifyServerCertificate=false"} is translated to sslMode=PREFERRED; {"useSSL=true", "requireSSL=true", "verifyServerCertificate=false"} is translated to sslMode=REQUIRED; {"useSSL=true" AND "verifyServerCertificate=true"} is translated to sslMode=VERIFY_CA. There is no equivalent legacy settings for sslMode=VERIFY_IDENTITY. Note that, for ALL server versions, the default setting of sslMode is PREFERRED, and it is equivalent to the legacy settings of useSSL=true, requireSSL=false, and verifyServerCertificate=false, which are different from their default settings for Connector/J 8.0.12 and earlier in some situations. Applications that continue to use the legacy properties and rely on their old default settings should be reviewed. The legacy properties are ignored if sslMode is set explicitly. If none of sslMode or useSSL is set explicitly, the default setting of sslMode=PREFERRED applies. Default: PREFERRED Since version: 8.0.13

因此，在我的例子中，设置sslMode=DISABLED就是解决这个问题所需要的全部内容。 这是在一台测试机器上。但是对于生产环境，安全解决方案应该正确配置Java客户机和MySQL服务器以使用SSL。

注意，通过禁用SSL，您可能还必须设置allowPublicKeyRetrieval=true。(同样，从安全角度来看，这不是一个明智的决定)。进一步的信息提供在MySQL ConnectionString选项:

AllowPublicKeyRetrieval If the user account uses sha256_password authentication, the password must be protected during transmission; TLS is the preferred mechanism for this, but if it is not available then RSA public key encryption will be used. To specify the server’s RSA public key, use the ServerRSAPublicKeyFile connection string setting, or set AllowPublicKeyRetrieval=True to allow the client to automatically request the public key from the server. Note that AllowPublicKeyRetrieval=True could allow a malicious proxy to perform a MITM attack to get the plaintext password, so it is False by default and must be explicitly enabled.