ERROR Streaming result set com.mysql.jdbc.RowDataDynamic@1d5a7f6 is still active. No statements may

最新推荐文章于 2023-09-13 15:45:08 发布
原创 最新推荐文章于 2023-09-13 15:45:08 发布 · 1.1w 阅读 · 0 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。

用sqoop导入mysql出现错误：

[jifeng@jifeng02 sqoop]$ bin/sqoop import --connect jdbc:mysql://10.X.X.X:3306/lir --username dss --password 123123 --table bb_month --hive-import -m 100
Warning: /home/jifeng/sqoop/../hcatalog does not exist! HCatalog jobs will fail.
Please set $HCAT_HOME to the root of your HCatalog installation.
Warning: /home/jifeng/sqoop/../accumulo does not exist! Accumulo imports will fail.
Please set $ACCUMULO_HOME to the root of your Accumulo installation.
Warning: $HADOOP_HOME is deprecated.

14/09/08 01:10:12 INFO sqoop.Sqoop: Running Sqoop version: 1.4.5
14/09/08 01:10:12 WARN tool.BaseSqoopTool: Setting your password on the command-line is insecure. Consider using -P instead.
14/09/08 01:10:12 INFO tool.BaseSqoopTool: Using Hive-specific delimiters for output. You can override
14/09/08 01:10:12 INFO tool.BaseSqoopTool: delimiters with --fields-terminated-by, etc.
14/09/08 01:10:12 INFO manager.MySQLManager: Preparing to use a MySQL streaming resultset.
14/09/08 01:10:12 INFO tool.CodeGenTool: Beginning code generation
14/09/08 01:10:12 INFO manager.SqlManager: Executing SQL statement: SELECT t.* FROM `bb_month` AS t LIMIT 1
14/09/08 01:10:12 ERROR manager.SqlManager: Error reading from database: java.sql.SQLException: Streaming result set com.mysql.jdbc.RowDataDynamic@1d5a7f6 is still active. No statements may be issued when any streaming result sets are open and in use on a given connection. Ensure that you have called .close() on any active streaming result sets before attempting more queries.
java.sql.SQLException: Streaming result set com.mysql.jdbc.RowDataDynamic@1d5a7f6 is still active. No statements may be issued when any streaming result sets are open and in use on a given connection. Ensure that you have called .close() on any active streaming result sets before attempting more queries.
        at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:930)
        at com.mysql.jdbc.MysqlIO.checkForOutstandingStreamingData(MysqlIO.java:2694)
        at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1868)
        at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2109)
        at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2642)
        at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2571)
        at com.mysql.jdbc.StatementImpl.executeQuery(StatementImpl.java:1464)
        at com.mysql.jdbc.ConnectionImpl.getMaxBytesPerChar(ConnectionImpl.java:3030)
        at com.mysql.jdbc.Field.getMaxBytesPerCharacter(Field.java:592)
        at com.mysql.jdbc.ResultSetMetaData.getPrecision(ResultSetMetaData.java:444)
        at org.apache.sqoop.manager.SqlManager.getColumnInfoForRawQuery(SqlManager.java:285)
        at org.apache.sqoop.manager.SqlManager.getColumnTypesForRawQuery(SqlManager.java:240)
        at org.apache.sqoop.manager.SqlManager.getColumnTypes(SqlManager.java:226)
        at org.apache.sqoop.manager.ConnManager.getColumnTypes(ConnManager.java:295)
        at org.apache.sqoop.orm.ClassWriter.getColumnTypes(ClassWriter.java:1773)
        at org.apache.sqoop.orm.ClassWriter.generate(ClassWriter.java:1578)
        at org.apache.sqoop.tool.CodeGenTool.generateORM(CodeGenTool.java:96)
        at org.apache.sqoop.tool.ImportTool.importTable(ImportTool.java:478)
        at org.apache.sqoop.tool.ImportTool.run(ImportTool.java:601)
        at org.apache.sqoop.Sqoop.run(Sqoop.java:143)
        at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:65)
        at org.apache.sqoop.Sqoop.runSqoop(Sqoop.java:179)
        at org.apache.sqoop.Sqoop.runTool(Sqoop.java:218)
        at org.apache.sqoop.Sqoop.runTool(Sqoop.java:227)
        at org.apache.sqoop.Sqoop.main(Sqoop.java:236)
14/09/08 01:10:12 ERROR tool.ImportTool: Encountered IOException running import job: java.io.IOException: No columns to generate for ClassWriter
        at org.apache.sqoop.orm.ClassWriter.generate(ClassWriter.java:1584)
        at org.apache.sqoop.tool.CodeGenTool.generateORM(CodeGenTool.java:96)
        at org.apache.sqoop.tool.ImportTool.importTable(ImportTool.java:478)
        at org.apache.sqoop.tool.ImportTool.run(ImportTool.java:601)
        at org.apache.sqoop.Sqoop.run(Sqoop.java:143)
        at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:65)
        at org.apache.sqoop.Sqoop.runSqoop(Sqoop.java:179)
        at org.apache.sqoop.Sqoop.runTool(Sqoop.java:218)
        at org.apache.sqoop.Sqoop.runTool(Sqoop.java:227)
        at org.apache.sqoop.Sqoop.main(Sqoop.java:236)

网上搜索是mysql的bug，下载新的jar就可以了 

[jifeng@jifeng02 ~]$ wget http://dev.mysql.com/get/Downloads/Connector-J/mysql-connector-java-5.1.32.tar.gz
--2014-09-08 01:20:16--  http://dev.mysql.com/get/Downloads/Connector-J/mysql-connector-java-5.1.32.tar.gz
正在解析主机 dev.mysql.com... 137.254.60.11
正在连接 dev.mysql.com|137.254.60.11|:80... 已连接。
已发出 HTTP 请求，正在等待回应... 302 Found
位置：http://cdn.mysql.com/Downloads/Connector-J/mysql-connector-java-5.1.32.tar.gz [跟随至新的 URL]
--2014-09-08 01:20:21--  http://cdn.mysql.com/Downloads/Connector-J/mysql-connector-java-5.1.32.tar.gz
正在解析主机 cdn.mysql.com... 23.41.85.226
正在连接 cdn.mysql.com|23.41.85.226|:80... 已连接。
已发出 HTTP 请求，正在等待回应... 200 OK
长度：3795067 (3.6M) [application/x-tar-gz]
正在保存至: “mysql-connector-java-5.1.32.tar.gz”

40% [============================>                                             ] 1,518,632    488K/s eta(英国中部时44% [================================>                                         ] 1,696,736    508K/s eta(英国中部时48% [===================================>                                      ] 1,854,568    523K/s eta(英国中部时54% [=======================================>                                  ] 2,052,944    543K/s eta(英国中部时57% [=========================================>                                ] 2,186,160    563K/s eta(英国中部时60% [===========================================>                              ] 2,302,000    572K/s eta(英国中部时63% [=============================================>                            ] 2,404,808    579K/s eta(英国中部时66% [================================================>                         ] 2,535,128    590K/s eta(英国中部时70% [==================================================>                       ] 2,656,760    601K/s eta(英国中部时73% [=====================================================>                    ] 2,803,008    613K/s eta(英国中部时77% [========================================================>                 ] 2,939,120    624K/s eta(英国中部时81% [===========================================================>              ] 3,104,192    645K/s eta(英国中部时85% [==============================================================>           ] 3,257,680    656K/s eta(英国中部时90% [==================================================================>       ] 3,437,232    669K/s eta(英国中部时95% [=====================================================================>    ] 3,609,544    681K/s eta(英国中部时100%[=========================================================================>] 3,795,067    698K/s   in 6.2s    

2014-09-08 01:20:27 (597 KB/s) - 已保存 “mysql-connector-java-5.1.32.tar.gz” [3795067/3795067])


API Streaming Failed 400 ＜400＞InternalError.Algo.InvalidParameter input content must be a string解决方案
weixin_43178406的博客
06-20 3万+
本文主要介绍了API Streaming Failed 400 <400> InternalError.Algo.InvalidParameter input content must be a string解决方案，希望能对使用vscode中cline的同学们有所帮助。 文章目录 1. 问题描述 2. 解决方案
Roo Code API Streaming Failed 400 InternalError.Algo.InvalidParameter input content must be string解决
热门推荐
weixin_43178406的博客
06-21 3万+
本文主要介绍了在Roo Code出现 API Streaming Failed 400 InternalError.Algo.InvalidParameter input content must be a string解决方案，希望能对使用vscode中Roo Code的同学们有所帮助。 文章目录 1. 问题描述 2. 解决方案
No statements may be issued when any streaming result sets are open and in use on a given connection
小妖666个人笔记
09-18 3580
eclipse下面的错误，注意下面错误中标红字体处。 Streaming result set com.mysql.jdbc.RowDataDynamic@cf13b1 is still active. No statements may be issued when any streaming result sets are open and in use on a given connect...
java.sql.SQLException: Streaming result set com.mysql.jdbc.RowDataDynamic@44f16719 is still active.
ToLightElegantly的博客
07-30 857
sqoop 导入mysql 表时,出现以下异常: 19/07/28 07:44:44 ERROR manager.SqlManager: Error reading from database: java.sql.SQLException: Streaming result set com.mysql.jdbc.RowDataDynamic@1ea9f6af is still active. No statements may be issued when any streaming result sets
【Spark】集群运行报错 --- java.lang.ClassNotFoundException: com.mysql.cj.jdbc.Driver
懂得一千零一种,赋予你失败的方法！
08-20 2044
报错 集群模式运行Spark的jar包时jdbc连接错误，无法连接数据库，我的数据库版本是5.x Caused by: java.lang.ClassNotFoundException: com.mysql.cj.jdbc.Driver at java.net.URLClassLoader.findClass(URLClassLoader.java:381) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at java.lang.C.
The specified datastore driver ("com.mysql.jdbc.Driver") was not found in the CLASSPATH
weixin_43616627的博客
01-13 4424
The specified datastore driver (“com.mysql.jdbc.Driver”) was not found in the CLASSPATH. Please check your CLASSPATH specification, and the name of the driver已解决 要执行的代码如下： object HiveRead { def mai...
【flink1.14.4】No operators defined in streaming topology. Cannot execute.
m0_37306331的博客
04-08 7770
org.apache.flink.client.program.ProgramInvocationException: The main method caused an error: No operators defined in streaming topology. Cannot execute. The program finished with the following exception: org.apache.flink.client.program.ProgramInvocation
java.sql.SQLException: Streaming result set com.mysql.jdbc.RowDataDynamic@27ce24aa is still active
翎野君的博客
03-20 2206
在Sqoop往mysql导出数据的时候报了这个错误，一开始还以为是jar包没有打进去或者打错位置了，未解便上网查询。 Error reading from database: java.sql.SQLException: Streaming result set com.mysql.jdbc.RowDataDynamic@27ce24aa is still active. No stateme...
解决问题 Sqoop No statements may be issued when any streaming result sets are open and in use
东语的专栏
09-13 634
sqoop 执行import或者export时候，出现错误。Sqoop No statements may be issued when any streaming result sets are open and in use
Sqoop No statements may be issued when any streaming result sets are open and in use on a given conn
好民小张的博客
03-09 948
Sqoop import命令报错 No statements may be issued when any streaming result sets are open and in use on a given connection. Ensure that you have called .close() on any active streaming result sets before attempting more queries. 1.原命令: sqoop import --connect jd
mysql resultset size_记一个MySQLStreamingresultset时的小错误
weixin_31567239的博客
01-21 829
同事使用kettle迁移MySQL数据时出现了 SQLException，详细报错信息如下：Error reading from database: java.sql.SQLException: Streaming result set com.mysql.jdbc.RowDataDynamic@xxxxxxx is still active. No statements may be issue...
sqoop Streaming result set com.mysql.jdbc.RowDataDynamic is still active
fanchw的专栏
07-06 1881
2020-07-06 11:20:56,735 ERROR manager.SqlManager: Error reading from database: java.sql.SQLException: Streaming result set com.mysql.jdbc.RowDataDynamic@7a2bfad9 is still active. No statements may be issued when any streaming result sets are open and in us
访问数据库的时候出现错误 Operation not allowed for a result set of type ResultSet.TYPE_FORWARD_ONLY.详解
Protinx的博客
04-22 3612
问题描述： 访问数据库的时候出现错误 Operation not allowed for a result set of type ResultSet.TYPE_FORWARD_ONLY. 解决方法： 在创建statement时这样创建： Statement stmt = conn.createStatement(ResultSet.TYPE_SCROLL_INSENSITIVE, ResultSet.CONCUR_UPDATABLE); 好了，问题就解决了哈 ...
mysql streaming_记一个 MySQL Streaming result set 时的小错误
weixin_35599933的博客
02-01 3087
同事使用kettle迁移MySQL数据时出现了 SQLException，详细报错信息如下：经查询MySQL官方文档(MySQL版本 5.1-8.0 一样)，发现报错原因是JDBC没有处理完resultSet结果集时又使用同一个connection提交了新的query。下面是官方文档对ResultSet的JDBC实现说明：默认情况下，ResultSet会一次性返回结果集并保存在内存中。这也是最有效...
S0L 错误 [$1 000]: Streaming result set com.mysql.d,protocol.a.result.ResultsetRowsStreaming@76a5bc65 is stll active. Nostatements may be issued when any streaming result sets are open and in use on a given connection, Ensure that you have caled.close() on any active streaming result sets before attempting more queries.
最新发布
07-31
在使用 MySQL 时，如果遇到 `S0L error [$1 000]: Streaming result set is still active` 错误，表明当前正在尝试执行新的查询，但前一个查询返回的流式结果集（streaming result set）尚未完全关闭。这种情况通常发生在使用 JDBC 驱动程序并启用流式查询（`useCursorFetch=true`）时。 ### 错误原因 MySQL 的 JDBC 驱动允许通过流式方式获取查询结果，特别是在处理大量数据时，这种方式可以有效减少内存占用。然而，流式结果集要求在获取完所有数据之前保持连接处于占用状态。如果在未完全读取完流式结果集时尝试执行新的查询，就会触发该错误[^1]。 ### 解决方案 #### 1. 正确关闭 `ResultSet` 确保在执行新查询之前，将前一个查询的 `ResultSet` 显式关闭。这可以通过在使用完 `ResultSet` 后调用其 `close()` 方法来实现。 ```java try (Statement stmt = connection.createStatement(); ResultSet rs = stmt.executeQuery("SELECT * FROM large_table")) { while (rs.next()) { // 处理数据 } } catch (SQLException e) { e.printStackTrace(); } ``` #### 2. 禁用流式查询 如果不需要流式处理功能，可以在 JDBC 连接字符串中禁用流式查询，通过设置 `useCursorFetch=false` 来避免此类问题。 ```java String url = "jdbc:mysql://localhost:3306/mydb?useCursorFetch=false"; ``` #### 3. 使用 `connection` 的 `setAutoCommit` 模式 在某些情况下，事务管理不当也可能导致流式结果集未能及时释放。确保在适当的时候提交事务或回滚事务，以释放相关资源。 ```java connection.setAutoCommit(false); // 执行查询并处理结果集 connection.commit(); ``` #### 4. 确保 `Statement` 和 `PreparedStatement` 被关闭 除了关闭 `ResultSet`，还应确保关联的 `Statement` 或 `PreparedStatement` 被正确关闭，以释放底层资源。 ### 最佳实践 - 始终在 `try-with-resources` 语句中使用 `ResultSet`、`Statement` 和 `Connection`，以确保资源在使用完毕后自动关闭。 - 避免在未完全读取流式结果集的情况下执行新查询。 - 在不需要流式处理时，禁用流式查询功能以简化资源管理。
评论 3
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
红包 添加红包
表情包 插入表情
表情包 代码片
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值