JDBC Session Stays In The Database After The Java Program Was Canceled Using CTRL + C
(Doc ID 1394687.1)
Last updated on MARCH 11, 2022
Applies to:JDBC - Version 22.214.171.124 and later
Information in this document applies to any platform.
An application that is using JDBC Thin driver changes in behavior when it is migrated from 10g to 11g version.
- Before the upgrade when pressing CTRL + C the application finished closing the connection to the database and also the session in the database is closed quickly.
- After the JDBC upgraded when the CTRL + C is pressed the connection to the database is closed, but the session in the database is still open for up to 15 minutes.
It is expected that using the 11g JDBC driver the CTRL + C closes the connection to the database, but also in the database the session is also closed.
Running the testcase using the 10g driver and pressing the CTRL + C the connection and the session is closed in the database, but when using the 11g driver the session in the database keeps open.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document