Either you or Spring should close() the Statements after use.
> Since Spring's JdbcTemplate seems to create a new Statement or
> PreparedStatement for each query, the fact that the newest versions of
> the driver keep all the statements for the duration of the connection
> causes impressive memory leaks.
>
> As far as I understand, the removal of weak references and early
> finalization of the statements from the driver is connected with
> threading issues and should not be reverted. But what can be done to
> avoid the issue, short of not using Spring?
>
> Can anyone suggest any workaround, or is this supposed to be solved in
> the driver eventually?
____________________________________________________________________________________
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. Try it now.
http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
--~--~---------~--~----~------------~-------~--~----~
Mailing List: http://groups.google.com/group/sqlitejdbc?hl=en
To unsubscribe, send email to [EMAIL PROTECTED]
-~----------~----~----~----~------~----~------~--~---
