-
Notifications
You must be signed in to change notification settings - Fork 46
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
Expected Behavior of Abort with the AWS JDBC Wrapper #1173
Comments
Hi @kiichiro-ito, thank you for reaching out and raising this issue. Could you please clarify whether you are interrupting the long-running query with |
Hi @aaron-congo. Thanks for your response! I'm sending When Spring Boot receives a SIGINT, Below is a thread dump captured during this behavior.
Maven dependencies:
thank you. |
I'm developing an application that connects to PostgreSQL via JDBC using Spring Boot and HikariCP.
When attempting to stop the application (sending SIGINT) while a long-running query is active, it seems that HikariCP waits for the query to complete before aborting the connection. This behavior appears to be related to the AWS JDBC Wrapper's implementation:
(https://github.com/aws/aws-advanced-jdbc-wrapper/blob/main/wrapper/src/main/java/software/amazon/jdbc/util/WrapperUtils.java#L186)
In contrast, when using only the standard PostgreSQL driver, the connection is forcibly terminated even if a long-running query is in progress.
Question:
Is there a configuration or method to avoid this behavior?
According to the java.sql.Connection#abort specification, the connection should be forcibly terminated.
Thank you.
The text was updated successfully, but these errors were encountered: