Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BatchPreparedStatementExecutor ArrayIndexOutOfBoundsException! #30696

Closed
CodingJabber opened this issue Mar 29, 2024 · 3 comments
Closed

BatchPreparedStatementExecutor ArrayIndexOutOfBoundsException! #30696

CodingJabber opened this issue Mar 29, 2024 · 3 comments
Labels

Comments

@CodingJabber
Copy link

CodingJabber commented Mar 29, 2024

Bug Report

For English only, other languages will not accept.

Before report a bug, make sure you have:

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?

4.0.0-RC1

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

ShardingSphere-JDBC

Expected behavior

execute success

Actual behavior

throw java.lang.ArrayIndexOutOfBoundsException: 0
at org.apache.shardingsphere.shardingjdbc.executor.BatchPreparedStatementExecutor.accumulate(BatchPreparedStatementExecutor.java:192)

Reason analyze (If you can)

this is same object, but not equals, I do not know why?It resulted in no SQL being executed, subsequently causing an exception when attempting to retrieve the affected count.
image

I think these two have the same problem:
#1419 #8577

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).

@strongduanmu
Copy link
Member

Hi @CodingJabber, can you try the latest 5.4.1? 4.0.0 is too old.

Copy link

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

@github-actions github-actions bot added the stale label Apr 29, 2024
@RaigorJiang
Copy link
Contributor

Closed due to no response.
If this problem persists, please reopen it or submit a new one.

@RaigorJiang RaigorJiang closed this as not planned Won't fix, can't repro, duplicate, stale May 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants