[
https://issues.apache.org/jira/browse/DERBY-3908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639843#action_12639843
]
Rick Hillegas commented on DERBY-3908:
--------------------------------------
Hi Bernt. I think that implementing Statement.cancel() would be a good idea and
it could also be the basis of a general solution. The problem case I'm
concerned about is the runaway transaction started by another user--in this
situation you still need some way to lookup the other user's Statement.
> Add a mechanism for cancelling runaway transactions.
> ----------------------------------------------------
>
> Key: DERBY-3908
> URL: https://issues.apache.org/jira/browse/DERBY-3908
> Project: Derby
> Issue Type: New Feature
> Components: SQL
> Reporter: Rick Hillegas
>
> We should add a mechanism by which the DBA can cancel a runaway transaction.
> Perhaps we could implement this as a new system procedure. This issue comes
> up on the user list frequently. For instance, see this thread:
> http://www.nabble.com/cancel-a-running-query--td19903183.html#a19903183 On
> the implementation side, Knut points out that
> EmbedConnection.cancelRunningStatement() might be a useful place to start.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
