My Oracle Support Banner

Threads Stuck on Jdbc.driver.CancelLock.exitExecuting With JDBC (Doc ID 2061757.1)

Last updated on FEBRUARY 10, 2022

Applies to:

JDBC - Version to [Release 11.2 to 12.1]
Information in this document applies to any platform.


Application using ojdbc7.jar version experiences stuck threads during execution.
The issue occurs when in a failure test the Oracle Listener is stopped, the Oracle Database sessions are killed, and then the Oracle Listener is restarted while the application is processing transactions.
After these steps are performed, sometimes one or more threads are stuck after the sessions have been killed. The stack trace is always similar to the following:
"G_M405T285|utx:7a7b49f8:14de7b67de7:-1aaa|chnl:L-XXX1-STP-01_TransactionQueue-Global" prio=10 tid=<TID> nid=<NID> in Object.wait()
  java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(
at oracle.jdbc.driver.CancelLock.exitExecuting(
- locked <0x00000004d37c3c00> (a oracle.jdbc.driver.CancelLock)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(
at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(
at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(
- locked <0x00000004d37c4078> (a oracle.jdbc.driver.T4CConnection)
at oracle.jdbc.driver.OraclePreparedStatementWrapper.executeUpdate(
There is the need to stop the JVM to clear the situation.




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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.