Statement.cancel() does not work

[kassak]

Describe the bug

Statement.cancel() does not work as it is invoked through software.aws.rds.jdbc.mysql.shading.com.mysql.cj.jdbc.ha.ConnectionProxy.JdbcInterfaceProxy#invoke which synchronises on statement instance.
As the result if I have the long running execute() (eg select sleep(314159265)) and trying to cancel it from another thread, cancel operation would wait until execute completes. That is definitely not the way cancel should work :)

Expected Behavior

Statement immediately canceled in the database, execute is immediately aborted with exception.

Current Behavior

Cancel is hung until execute completes

Reproduction Steps

execute select sleep(314159265) on one thread and try to cancel statement from another thread

Possible Solution

No response

Additional Information/Context

No response

The AWS JDBC Driver for MySQL version used

1.1.9

JDK version used

21

Operating System and version

Linux 6.6.9-arch1-1 #1 SMP PREEMPT_DYNAMIC Tue, 02 Jan 2024 02:28:28 +0000 x86_64 GNU/Linux

[crystall-bitquill]

Hi @kassak,

Thanks for reaching out and raising this issue.

We'll take a look at this and keep you updated as we investigate.

And to let you know, while the AWS JDBC Driver for MySQL is still being maintained at the moment, new features will no longer be added to the driver and all future developments will take place in the AWS JDBC Driver project. More details can be found on the maintenance policy. We encourage users of the AWS JDBC Driver for MySQL to try out the AWS JDBC Driver, as it provides similar and additional features. There is a migration guide available here.

Thank you for you patience!

[crystall-bitquill]

Hi @kassak,

We've recently merged in a fix (#531). Could you kindly check out our latest snapshot build and let us know if the issue persists?

Thank you!

[crystall-bitquill]

Hi @kassak,

The fix for this issue is now available on the latest version of the AWS JDBC Driver for MySQL. If there are no further updates on this ticket in the next few days, it will be closed. Please feel free to reopen this issue or to create a new one if the issue persists or if you have additional questions or concerns.

Thank you!