db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lily Wei (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-4560) ij should remove async statements from session after completion
Date Thu, 17 Feb 2011 17:27:24 GMT

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

Lily Wei updated DERBY-4560:
----------------------------

              Urgency: Normal
    Affects Version/s: 10.6.2.1
                       10.7.1.1
               Labels: derby_triage10_8 ij  (was: ij)

> ij should remove async statements from session after completion
> ---------------------------------------------------------------
>
>                 Key: DERBY-4560
>                 URL: https://issues.apache.org/jira/browse/DERBY-4560
>             Project: Derby
>          Issue Type: Bug
>          Components: Tools
>    Affects Versions: 10.6.1.0, 10.6.2.1, 10.7.1.1
>            Reporter: Sylvain Leroux
>              Labels: derby_triage10_8, ij
>
> ij has statements to execute (ASYNC) and join (WAIT FOR) asynchronous statements.
> Asynchronous statements are stored in the corresponding Session object. but - as far
as I can see - are never removed. This leads to memory leaks:
>   ij> CONNECT 'jdbc:derby:memory:dummy;create=true';
>   ij> WAIT FOR stmt;
>   IJ ERROR: No async statement exists with the name STMT
>   ij> ASYNC stmt 'VALUES(1),(2),(3)';
>   ij> WAIT FOR stmt;
>   1          
>   -----------
>   1          
>   2          
>   3          
>   
>   3 rows selected
>   ij> WAIT FOR stmt;
>   ERROR XJ012: 'Statement' already closed.
> After completion, WAIT FOR should remove the async statement from the session since it
is no longer useful.

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

        

Mime
View raw message