Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
10.6.1.0, 10.6.2.1, 10.7.1.1
-
None
-
Normal
-
Newcomer, Repro attached
Description
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.