You are viewing a plain text version of this content. The canonical link for it is here.

Posted to derby-dev@db.apache.org by "Dag H. Wanvik (JIRA)" <ji...@apache.org> on 2011/08/05 23:24:27 UTC

[jira] [Updated] (DERBY-5375) Memory "leak" when setting a query timeout

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

Dag H. Wanvik updated DERBY-5375:
---------------------------------

    Bug behavior facts: [Seen in production]

> Memory "leak" when setting a query timeout
> ------------------------------------------
>
>                 Key: DERBY-5375
>                 URL: https://issues.apache.org/jira/browse/DERBY-5375
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC
>    Affects Versions: 10.8.1.2
>            Reporter: Thomas Brandl
>
> When setting a query timeout, a new CancelQueryTask is created and scheduled. This CancelQueryTask is still held in the java.util.Timer class's task queue even when the query is already finished until the query timeout is reached.
> For example, if i set a query timeout of 2h using statement.setQueryTimeout(7200) this means that the CancelQueryTask will remain for 2 hours even if the query is finished within 1 second. In scenarios with high load, this can lead to Out of Memory Situations.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira