Statements in the HarvestDatabase are often not being closed after use
Field Tab
Test
Field Tab
Test
Description
When running the TEST11B with the Derby that stresses the admin DB (a.k.a archive DB), we found that after moving the connectionpool system used by the harvestDatabase, ressources are not being released, if we do not closes the preparedStatents after use.
It might not be an issue with PostgreSQL or MySQL, but it certainly is with Derby. (See bug ). Some of the problems we have experienced with Derby could be related to that.
Attachments
3
Checklist
Activity
Show:
SrNovember 18, 2011 at 3:06 PM
Edited
runtimeinfo-data-p8168.txt contains a list of open statements in the derby database (harvestDatabase) used with NAS r2184. (after fixing this bug). runtimeinfo-data-p8169.txt contains a list of open statements in the derby database (adminDatabase) used with NAS r2184. (after fixing this bug).
SrNovember 18, 2011 at 2:59 PM
Fixed in r2184
SrNovember 18, 2011 at 11:27 AM
Run on the 3.16 branch we get 43 such warnings.
SrNovember 17, 2011 at 4:57 PM
44 warnings about PreparedStatements not being closed in src/
When running the TEST11B with the Derby that stresses the admin DB (a.k.a archive DB), we found that after moving the connectionpool system used by the harvestDatabase, ressources are not being released, if we do not closes the preparedStatents after use.
It might not be an issue with PostgreSQL or MySQL, but it certainly is with Derby. (See bug ). Some of the problems we have experienced with Derby could be related to that.