-
Bug
-
Resolution: Done
-
Critical
-
WildFly/IronJacamar 1.3.4.Final, 1.2.7.Final
-
None
Hi,
in our application we are using the Statement.cancel() method to stop long-running queries; in Wildfly 9.0.2 this is not working because the cancel() method is synchronized using a lock which is not released until the query is executed. In WrappedStatement:
public void cancel() throws SQLException { if (doLocking) lock(); try { /* ... */
It seems this behaviour has changed from version 1.2.5.Final of ironjacamar-jdbc; in version 1.2.4.Final WrappedStatement.cancel doesn't try to obtain the lock.
Probably I'm missing something, but to me it's strange that in order to cancel a statement you have to wait for its completion.
Thank you,
lorenzo
- is incorporated by
-
JBEAP-5084 Statement.cancel() is not invoked until the statement is completed
- Verified
-
JBEAP-6593 (7.0.z) JBJCA-1321 - Statement.cancel() is not invoked until the statement is completed
- Closed
-
WFLY-8258 Upgrade to IronJacamar 1.3.6
- Closed