db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mamta A. Satoor (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-3908) Add a mechanism for cancelling runaway transactions.
Date Sun, 30 Sep 2012 02:12:07 GMT

     [ https://issues.apache.org/jira/browse/DERBY-3908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Mamta A. Satoor updated DERBY-3908:

    Urgency: Normal
     Labels: derby_triage10_10  (was: )
> 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
>              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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message