kettle数据库连接问题

最新推荐文章于 2024-06-07 16:26:36 发布
最新推荐文章于 2024-06-07 16:26:36 发布
阅读量1.8k 收藏 1
点赞数 1
分类专栏： 大学四年所写 文章标签： 大数据
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/kokool/article/details/124577766
版权

实验环境：
mysql server版本是5.7+
jdk是1.8

另外我在kettle 的lib文件夹下放入了相应版本的mysql-connect-jre包（这个也是要跟你的mysql server版本对应上，一般都是5.1.17以上）

在这里插入图片描述

问题的可能原因：

  1. mysql的版本是最新的8（本博客不解决这个问题）
  2. 主机名称有误（也即地址有误）
  3. 数据库名写错了（即没有这个数据）

总结：粗心大意

地址错误的提示日志：

就下面这一句是核心，有的会说地址冲突，不过你单机环境怎么可能会有这个问题

The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.

错误连接数据库 [root] : org.pentaho.di.core.exception.KettleDatabaseException: 
Error occurred while trying to connect to the database

Error connecting to database: (using class org.gjt.mm.mysql.Driver)
Communications link failure

The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.


org.pentaho.di.core.exception.KettleDatabaseException: 
Error occurred while trying to connect to the database

Error connecting to database: (using class org.gjt.mm.mysql.Driver)
Communications link failure

The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.


	at org.pentaho.di.core.database.Database.normalConnect(Database.java:472)
	at org.pentaho.di.core.database.Database.connect(Database.java:370)
	at org.pentaho.di.core.database.Database.connect(Database.java:341)
	at org.pentaho.di.core.database.Database.connect(Database.java:331)
	at org.pentaho.di.core.database.DatabaseFactory.getConnectionTestReport(DatabaseFactory.java:83)
	at org.pentaho.di.core.database.DatabaseFactory.getConnectionTestResults(DatabaseFactory.java:112)
	at org.pentaho.di.core.database.DatabaseMeta.testConnectionSuccess(DatabaseMeta.java:2811)
	at org.pentaho.ui.database.event.DataHandler.testDatabaseConnection(DataHandler.java:621)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.pentaho.ui.xul.impl.AbstractXulDomContainer.invoke(AbstractXulDomContainer.java:313)
	at org.pentaho.ui.xul.impl.AbstractXulComponent.invoke(AbstractXulComponent.java:157)
	at org.pentaho.ui.xul.impl.AbstractXulComponent.invoke(AbstractXulComponent.java:141)
	at org.pentaho.ui.xul.swt.tags.SwtButton.access$500(SwtButton.java:43)
	at org.pentaho.ui.xul.swt.tags.SwtButton$4.widgetSelected(SwtButton.java:137)
	at org.eclipse.swt.widgets.TypedListener.handleEvent(Unknown Source)
	at org.eclipse.swt.widgets.EventTable.sendEvent(Unknown Source)
	at org.eclipse.swt.widgets.Display.sendEvent(Unknown Source)
	at org.eclipse.swt.widgets.Widget.sendEvent(Unknown Source)
	at org.eclipse.swt.widgets.Display.runDeferredEvents(Unknown Source)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Unknown Source)
	at org.eclipse.jface.window.Window.runEventLoop(Window.java:820)
	at org.eclipse.jface.window.Window.open(Window.java:796)
	at org.pentaho.di.ui.xul.KettleDialog.show(KettleDialog.java:80)
	at org.pentaho.di.ui.xul.KettleDialog.show(KettleDialog.java:47)
	at org.pentaho.di.ui.core.database.dialog.XulDatabaseDialog.open(XulDatabaseDialog.java:116)
	at org.pentaho.di.ui.core.database.dialog.DatabaseDialog.open(DatabaseDialog.java:61)
	at org.pentaho.di.ui.spoon.delegates.SpoonDBDelegate.newConnection(SpoonDBDelegate.java:495)
	at org.pentaho.di.ui.spoon.delegates.SpoonDBDelegate.newConnection(SpoonDBDelegate.java:482)
	at org.pentaho.di.ui.spoon.Spoon.newConnection(Spoon.java:8684)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.pentaho.ui.xul.impl.AbstractXulDomContainer.invoke(AbstractXulDomContainer.java:313)
	at org.pentaho.ui.xul.impl.AbstractXulComponent.invoke(AbstractXulComponent.java:157)
	at org.pentaho.ui.xul.impl.AbstractXulComponent.invoke(AbstractXulComponent.java:141)
	at org.pentaho.ui.xul.jface.tags.JfaceMenuitem.access$100(JfaceMenuitem.java:43)
	at org.pentaho.ui.xul.jface.tags.JfaceMenuitem$1.run(JfaceMenuitem.java:106)
	at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
	at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:545)
	at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:490)
	at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:402)
	at org.eclipse.swt.widgets.EventTable.sendEvent(Unknown Source)
	at org.eclipse.swt.widgets.Display.sendEvent(Unknown Source)
	at org.eclipse.swt.widgets.Widget.sendEvent(Unknown Source)
	at org.eclipse.swt.widgets.Display.runDeferredEvents(Unknown Source)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Unknown Source)
	at org.pentaho.di.ui.spoon.Spoon.readAndDispatch(Spoon.java:1381)
	at org.pentaho.di.ui.spoon.Spoon.waitForDispose(Spoon.java:7817)
	at org.pentaho.di.ui.spoon.Spoon.start(Spoon.java:9179)
	at org.pentaho.di.ui.spoon.Spoon.main(Spoon.java:707)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.pentaho.commons.launcher.Launcher.main(Launcher.java:92)
Caused by: org.pentaho.di.core.exception.KettleDatabaseException: 
Error connecting to database: (using class org.gjt.mm.mysql.Driver)
Communications link failure

The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.

	at org.pentaho.di.core.database.Database.connectUsingClass(Database.java:583)
	at org.pentaho.di.core.database.Database.normalConnect(Database.java:456)
	... 58 more
Caused by: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure

The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
	at com.mysql.jdbc.Util.handleNewInstance(Util.java:411)
	at com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:1121)
	at com.mysql.jdbc.MysqlIO.<init>(MysqlIO.java:358)
	at com.mysql.jdbc.ConnectionImpl.coreConnect(ConnectionImpl.java:2489)
	at com.mysql.jdbc.ConnectionImpl.connectOneTryOnly(ConnectionImpl.java:2526)
	at com.mysql.jdbc.ConnectionImpl.createNewIO(ConnectionImpl.java:2311)
	at com.mysql.jdbc.ConnectionImpl.<init>(ConnectionImpl.java:834)
	at com.mysql.jdbc.JDBC4Connection.<init>(JDBC4Connection.java:47)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
	at com.mysql.jdbc.Util.handleNewInstance(Util.java:411)
	at com.mysql.jdbc.ConnectionImpl.getInstance(ConnectionImpl.java:416)
	at com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:347)
	at java.sql.DriverManager.getConnection(DriverManager.java:664)
	at java.sql.DriverManager.getConnection(DriverManager.java:208)
	at org.pentaho.di.core.database.Database.connectUsingClass(Database.java:567)
	... 59 more
Caused by: java.net.UnknownHostException: localhos
	at java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method)
	at java.net.InetAddress$2.lookupAllHostAddr(InetAddress.java:928)
	at java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1323)
	at java.net.InetAddress.getAllByName0(InetAddress.java:1276)
	at java.net.InetAddress.getAllByName(InetAddress.java:1192)
	at java.net.InetAddress.getAllByName(InetAddress.java:1126)
	at com.mysql.jdbc.StandardSocketFactory.connect(StandardSocketFactory.java:249)
	at com.mysql.jdbc.MysqlIO.<init>(MysqlIO.java:308)
	... 74 more

主机名       : localhos
端口           : 3306
数据库名:test
没有该数据库的错误提示日志
错误连接数据库 [root] : org.pentaho.di.core.exception.KettleDatabaseException: 
Error occurred while trying to connect to the database

Error connecting to database: (using class org.gjt.mm.mysql.Driver)
Unknown database 'tes'


org.pentaho.di.core.exception.KettleDatabaseException: 
Error occurred while trying to connect to the database

Error connecting to database: (using class org.gjt.mm.mysql.Driver)
Unknown database 'tes'


	at org.pentaho.di.core.database.Database.normalConnect(Database.java:472)
	at org.pentaho.di.core.database.Database.connect(Database.java:370)
	at org.pentaho.di.core.database.Database.connect(Database.java:341)
	at org.pentaho.di.core.database.Database.connect(Database.java:331)
	at org.pentaho.di.core.database.DatabaseFactory.getConnectionTestReport(DatabaseFactory.java:83)
	at org.pentaho.di.core.database.DatabaseFactory.getConnectionTestResults(DatabaseFactory.java:112)
	at org.pentaho.di.core.database.DatabaseMeta.testConnectionSuccess(DatabaseMeta.java:2811)
	at org.pentaho.ui.database.event.DataHandler.testDatabaseConnection(DataHandler.java:621)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.pentaho.ui.xul.impl.AbstractXulDomContainer.invoke(AbstractXulDomContainer.java:313)
	at org.pentaho.ui.xul.impl.AbstractXulComponent.invoke(AbstractXulComponent.java:157)
	at org.pentaho.ui.xul.impl.AbstractXulComponent.invoke(AbstractXulComponent.java:141)
	at org.pentaho.ui.xul.swt.tags.SwtButton.access$500(SwtButton.java:43)
	at org.pentaho.ui.xul.swt.tags.SwtButton$4.widgetSelected(SwtButton.java:137)
	at org.eclipse.swt.widgets.TypedListener.handleEvent(Unknown Source)
	at org.eclipse.swt.widgets.EventTable.sendEvent(Unknown Source)
	at org.eclipse.swt.widgets.Display.sendEvent(Unknown Source)
	at org.eclipse.swt.widgets.Widget.sendEvent(Unknown Source)
	at org.eclipse.swt.widgets.Display.runDeferredEvents(Unknown Source)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Unknown Source)
	at org.eclipse.jface.window.Window.runEventLoop(Window.java:820)
	at org.eclipse.jface.window.Window.open(Window.java:796)
	at org.pentaho.di.ui.xul.KettleDialog.show(KettleDialog.java:80)
	at org.pentaho.di.ui.xul.KettleDialog.show(KettleDialog.java:47)
	at org.pentaho.di.ui.core.database.dialog.XulDatabaseDialog.open(XulDatabaseDialog.java:116)
	at org.pentaho.di.ui.core.database.dialog.DatabaseDialog.open(DatabaseDialog.java:61)
	at org.pentaho.di.ui.spoon.delegates.SpoonDBDelegate.newConnection(SpoonDBDelegate.java:495)
	at org.pentaho.di.ui.spoon.delegates.SpoonDBDelegate.newConnection(SpoonDBDelegate.java:482)
	at org.pentaho.di.ui.spoon.Spoon.newConnection(Spoon.java:8684)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.pentaho.ui.xul.impl.AbstractXulDomContainer.invoke(AbstractXulDomContainer.java:313)
	at org.pentaho.ui.xul.impl.AbstractXulComponent.invoke(AbstractXulComponent.java:157)
	at org.pentaho.ui.xul.impl.AbstractXulComponent.invoke(AbstractXulComponent.java:141)
	at org.pentaho.ui.xul.jface.tags.JfaceMenuitem.access$100(JfaceMenuitem.java:43)
	at org.pentaho.ui.xul.jface.tags.JfaceMenuitem$1.run(JfaceMenuitem.java:106)
	at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
	at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:545)
	at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:490)
	at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:402)
	at org.eclipse.swt.widgets.EventTable.sendEvent(Unknown Source)
	at org.eclipse.swt.widgets.Display.sendEvent(Unknown Source)
	at org.eclipse.swt.widgets.Widget.sendEvent(Unknown Source)
	at org.eclipse.swt.widgets.Display.runDeferredEvents(Unknown Source)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Unknown Source)
	at org.pentaho.di.ui.spoon.Spoon.readAndDispatch(Spoon.java:1381)
	at org.pentaho.di.ui.spoon.Spoon.waitForDispose(Spoon.java:7817)
	at org.pentaho.di.ui.spoon.Spoon.start(Spoon.java:9179)
	at org.pentaho.di.ui.spoon.Spoon.main(Spoon.java:707)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.pentaho.commons.launcher.Launcher.main(Launcher.java:92)
Caused by: org.pentaho.di.core.exception.KettleDatabaseException: 
Error connecting to database: (using class org.gjt.mm.mysql.Driver)
Unknown database 'tes'

	at org.pentaho.di.core.database.Database.connectUsingClass(Database.java:583)
	at org.pentaho.di.core.database.Database.normalConnect(Database.java:456)
	... 58 more
Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Unknown database 'tes'
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
	at com.mysql.jdbc.Util.handleNewInstance(Util.java:411)
	at com.mysql.jdbc.Util.getInstance(Util.java:386)
	at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1054)
	at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4237)
	at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4169)
	at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:928)
	at com.mysql.jdbc.MysqlIO.proceedHandshakeWithPluggableAuthentication(MysqlIO.java:1750)
	at com.mysql.jdbc.MysqlIO.doHandshake(MysqlIO.java:1290)
	at com.mysql.jdbc.ConnectionImpl.coreConnect(ConnectionImpl.java:2493)
	at com.mysql.jdbc.ConnectionImpl.connectOneTryOnly(ConnectionImpl.java:2526)
	at com.mysql.jdbc.ConnectionImpl.createNewIO(ConnectionImpl.java:2311)
	at com.mysql.jdbc.ConnectionImpl.<init>(ConnectionImpl.java:834)
	at com.mysql.jdbc.JDBC4Connection.<init>(JDBC4Connection.java:47)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
	at com.mysql.jdbc.Util.handleNewInstance(Util.java:411)
	at com.mysql.jdbc.ConnectionImpl.getInstance(ConnectionImpl.java:416)
	at com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:347)
	at java.sql.DriverManager.getConnection(DriverManager.java:664)
	at java.sql.DriverManager.getConnection(DriverManager.java:208)
	at org.pentaho.di.core.database.Database.connectUsingClass(Database.java:567)
	... 59 more

主机名       : localhost
端口           : 3306
数据库名:tes
克里姆颂
关注
  • 1
    点赞
  • 踩
  • 1
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
专栏目录
Kettle所有数据库数据库连接驱动Jar
08-19
在IT领域，数据库连接是数据集成过程中的关键环节，特别是在使用工具如Kettle（也称为Pentaho Data Integration，简称PDI）时。Kettle是一款强大的ETL（Extract, Transform, Load）工具，用于从各种数据源抽取数据，...
Mac下 Communications link failure，The last packet sent successfully to the server was 0 milliseconds
shao_feng_ocean的博客
05-22 1150
Mac必须允许用户远程访问数据库才能链接mysql 1、打开终端，进入MySQL之后 2、输入以下语句，进入mysql库： use mysql; 3、更新域属性，'%'表示允许外部访问： update user set host='%' where user ='root'; 4、执行以上语句之后再执行(刷新配置)： FLUSH PRIVILEGES; 5、再执行授权语句： GRANT ALL PRIVILEGES ON *.* TO 'root'@'%'WITH GRANT OPT.
The last packet sent successfully to the server was 0 milliseconds ago
sugar_cookie的博客
10-13 4万+
这里写自定义目录标题 今天在弄数据库迁移及部署到客户服务器时，发现启动成功了，但是数据请求超时，赶紧打开日志看一下，报了这样的错： The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server. at com.mysql.cj.jdbc.exceptions.SQLError.createCommunication
mysql突然远程连不上
最新发布
qq_33043025的博客
06-07 325
其他机器telnet3306端口超时，本机tcpdump查看仅有win，无ack，说明3306对外是联调的；本机telnet3306端口正常，防火墙已关闭，头一天给配置了域名；最终解决：先启动防火墙再关闭防火墙，挺莫名其妙的问题。
The last packet sent successfully to the server was 0 milliseconds ago.问题分析
qq_42865087的博客
06-30 2万+
mysql问题
The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received
weixin_39454319的博客
12-17 7180
The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.
解决MySQL报错：“The last packet sent successfully to the server was 0 milliseconds ago.”
培根芝士的专栏
09-07 2万+
方法就是将mysql回收空闲连接的时间变长，mysql默认回收时间是8小时，可以在mysql目录下的my.cnf中增加下面配置，将时间改为1天。之所以出现异常，是由于数据库回收了连接，而系统的缓冲池不知道，继续使用被回收的连接所致的。wait_timeout=86400 //加上这一句。
The last packet sent successfully to the server was 0 milliseconds ago. The
qq_27455063的博客
02-10 1万+
异常”The last packet sent successfully to the server was 0 milliseconds ago.“的原因 1.是由于数据库回收了连接，而系统的缓冲池不知道，继续使用被回收的连接所致的。 2.服务器断网 解决办法 第一种情况，将mysql回收空闲连接的时间变长，mysql默认回收时间是8小时，可以在mysql目录下的my.ini中增加下面配
kettle 7.1数据库连接驱动包
06-08
《Kettle 7.1数据库连接驱动包详解与应用》 Kettle，也称为Pentaho Data Integration（PDI），是一款强大的数据集成工具，广泛应用于数据清洗、转换和加载等任务。在使用Kettle进行数据库操作时，正确配置并选用...
Kettle常用数据库连接驱动
01-05
标题提到的“Kettle常用数据库连接驱动”是指Kettle支持的、用于与不同数据库系统通信的JDBC驱动。 【Oracle驱动】：ojdbc8.jar是Oracle数据库的JDBC驱动包，适用于Java 8及更高版本。Oracle数据库是企业级关系型...
kettle 连接 clickhouse数据库
03-23
2. **创建数据库连接**：在Kettle的数据源管理中，选择“New”创建一个新的数据库连接。在弹出的窗口中，选择“Other”作为数据库类型，然后在“Database type”字段中输入“ClickHouse”。 3. **配置连接参数**：...
Kettle简单参数化配置连接数据库
04-19
2. **配置数据库连接**：在“数据库连接”步骤中，选择“使用变量”选项，并在对应的字段中填入对应的参数名（如${DB_URL}、${DB_USER}和${DB_PASSWORD}）。 3. **传递参数值**：在运行Kettle作业或转换时，通过...
解决异常：“The last packet sent successfully to the server was 0 milliseconds ago. ”的办法；及Linux网络ping不通得问题
qq_21128741的博客
02-25 4万+
2com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure 3 The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server. 宿主机ping不通Linux
已解决The last packet sent successfully to the server was 0 milliseconds ago. The driver has not receiv
Huang405267467的博客
07-07 4万+
注：此文章是在mysql8版本的前提下编写的。在我们使用springcloud在连接mysql数据库时，有时会碰到如下这种异常： 为此我上网查了不少资料，在这里小总结一下：1. 连接url是否正确（自己看看useSSL是否为false）：2.数据库服务是否打开：找到MySql服务：3.网上最多解决的等待时间问题：（wait_timeout)我使用的mysql版本为 8.0.27 ，在用网上的修改my.ini配置文件时 mysql会直接报错，启动不了，即使临时修改wait_timeout时间，也是一样会报
mysql数据库连接报错The last packet sent successfully to the server was 0 milliseconds ago. The drive
flyf000的博客
08-16 1万+
mysql数据库连接报错The last packet sent successfully to the server was 0 milliseconds ago. The drive
The last packet sent successfully to the server was 0 milliseconds ago. 解决办法记录
热门推荐
apachesolr的博客
02-09 11万+
最近与第三方对接数据的时候，通过jdbc链接对方提供的数据库，总是提示一下错误 Exception in thread "main" com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received
连接到数据库mysql时报错:The last packet sent successfully to the server was 0 milliseconds ago. The driver ha
weixin_42331975的博客
06-24 7万+
       正在自学java中，目前在学习到数据库时，在用java驱动连接到数据库出现如下报错，网上搜了一下，发现并不能解决，其实像这类报错具有很多种可能，每个人的方法都只能作为参考，要完全解决问题，还是要不断尝试，我的方法仅供参考。The last packet sent successfully to the server was 0 milliseconds ago. The driver...
Kettle数据库连接优化与Join问题深度解析
首先，Kettle中的数据库连接管理非常重要。它采用单步一连接的模式，通过设置数据库连接池，用户可以配置初始连接数和最大连接数，这有助于优化性能，特别是在处理大量并发请求时。Pooling选项卡提供了灵活的配置，...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值