db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Brandl (JIRA)" <j...@apache.org>
Subject [jira] [Created] (DERBY-5375) Memory "leak" when setting a query timeout
Date Fri, 05 Aug 2011 11:43:27 GMT
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:
            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


View raw message