org.apache.shardingsphere.driver.jdbc.core.statement.ShardingSpherePreparedStatement#getResultSets，repeat resultSet

[LeavesGirl]

Bug Report

For English only, other languages will not accept.

Before report a bug, make sure you have:

• Searched open and closed GitHub issues.
• Read documentation: ShardingSphere Doc.

Please pay attention on issues you submitted, because we maybe need more details.
If no response anymore and we cannot reproduce it on current information, we will close it.

Please answer these questions before submitting your issue. Thanks!

Which version of ShardingSphere did you use?

5.4.1

Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?

ShardingSphere-JDBC

Expected behavior

---

//{conn-10006, pstmt-20499, rs-51029} closed
{conn-10006, pstmt-20499, rs-51028} closed
//{conn-10006, pstmt-20500, rs-51031} closed
{conn-10006, pstmt-20500, rs-51030} closed

Actual behavior

---

{conn-10006, pstmt-20499, rs-51029} closed
{conn-10006, pstmt-20499, rs-51028} closed
{conn-10006, pstmt-20500, rs-51031} closed
{conn-10006, pstmt-20500, rs-51030} closed

Reason analyze (If you can)

private List<ResultSet> getResultSets() throws SQLException {
        List<ResultSet> result = new ArrayList<>(statements.size());
        for (Statement each : statements) {
            if (null != each.getResultSet()) {
                result.add(each.getResultSet());
            }
        }
        return result;
    }

each.getResultSet(), this codes would make a new instanceof resultSet，so the com.alibaba.druid.filter.Filter#resultSet_close will be called twice. com.alibaba.druid.filter.stat.StatFilterContext#addFetchRowCount,this rowCount added twice, is fault.

Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc.

Example codes for reproduce this issue (such as a github link).

[terrymanu]

There are lots of messages, but no interaction among the issue reporters, which could lead to misunderstandings.
I think this issue does not describe the problem clearly.
Can you explain again?

[github-actions]

There hasn't been any activity on this issue recently, and in order to prioritize active issues, it will be marked as stale.