I am having a problem where the lock on the database is not being released. I am using database connection pooling and I am just running a test app and certainly DO close my connections. I double checked that the code that closes the connection is being called and it is.
What other things can I check or might be doing wrong?
I am using the M$ Access as the database and the odbc bridge driver to get to it.
When I shut down the server I would expect that the database pooling releases all its connections. It does look like it though, since I still still the databaseName.ldb file in that directory (MS Access way of lock the database file).
I know that Sun says that it is not production level driver. 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 leads me to believe that it's NOT the driver problem, but my configuration problem.
I am attaching the server.xml file just in case that would help in solving the problem.
--------------------------------------------------------------------- To unsubscribe, e-mail: tomcat-user-unsubscribe@(protected) For additional commands, e-mail: tomcat-user-help@(protected)