A common problem in beginner JDBC is not performing a ROLLBACK when an update fails. Even when autocommit is set to TRUE, a failed update will leave the records locked in the database. Update statements should always be coded so that if an exception is thrown, a rollback is performed on the connection.
-----Original Message----- From: SH Solutions [mailto:[EMAIL PROTECTED] Sent: Sunday, December 07, 2003 10:51 AM To: 'Tomcat Users List' Subject: AW: Lock on database file not being released... Hi > However, I have used this driver before in a standalone app and when you close a connection, it certainly does release the lock on the database file. This makes me think, you didn't use pooling in this standalone app. Therefor check weather you close all your ResultSets and Statements. In standalone apps where no pooling is involved, they are caught by the garbage collector, but not in connection pooling. Trapped into this myself. cu Steffen --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
