[
https://issues.apache.org/jira/browse/DERBY-3908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16569190#comment-16569190
]
Rick Hillegas commented on DERBY-3908:
--------------------------------------
I'm not aware that anyone has worked on this issue. Here is the implementation
of EmbedStatement.cancel(), the low bar for this feature:
{noformat}
/**
* Cancel can be used by one thread to cancel a statement that
* is being executed by another thread.
* @exception SQLException thrown on failure.
*/
public void cancel() throws SQLException {
throw Util.notImplemented("cancel");
}
{noformat}
> Add a mechanism for cancelling runaway transactions.
> ----------------------------------------------------
>
> Key: DERBY-3908
> URL: https://issues.apache.org/jira/browse/DERBY-3908
> Project: Derby
> Issue Type: Improvement
> Components: SQL
> Reporter: Rick Hillegas
> Priority: Major
> Labels: derby_triage10_10
>
> 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 was sent by Atlassian JIRA
(v7.6.3#76005)
