OK, I now think I know the issue. Try changing the entries for the ODBC
connection. Specifically change:

ImplicitCommitSync

And

UserCommitSync

The docs are inconsistent on their usage, and I think the drivers vary
depending upon the version of the Jet engine you are using.

Anyhow, adjust these and see what happens.



-----Original Message-----
From: Chaikin, Yaakov Y (US SSA)
[mailto:yaakov.y.chaikin@(protected)]
Sent: Sunday, December 07, 2003 2:13 PM
To: Tomcat Users List
Subject: RE: Lock on database file not being released...


> > 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.

Steffen,

I tried what you said and closed the ResultSet and Statement before I
close the Connection. Still same affect.

Any other ideas anyone?

I highly doubt it's the driver. I would bet that I am doing something
wrong. I just can't figure out what it is.

Thanks,
Yaakov.


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@(protected)
For additional commands, e-mail: tomcat-user-help@(protected)



---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@(protected)
For additional commands, e-mail: tomcat-user-help@(protected)