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.
|Bug behavior facts||[Seen in production]|
|Workflow||jira [ 12626321 ]||Default workflow, editable Closed status [ 12801731 ]|