You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user-java@ibatis.apache.org by AlexeyG <ag...@z-techcorp.com> on 2006/07/28 21:47:27 UTC
MS Access LDB locks using JDBC-ODBC bridge and iBATIS
Hello,
I am attempting to use iBATIS and to access MS Access file via JDBC-ODBC
bridge.
(I am using Spring's "SqlMapClientDaoSupport," but that is probably
irrelevant)
All this runs on Tomcat... First time DB gets accessed the LDB lock file is
created. From there on the only way I can remove the lock file is to kill
the JVM...
Any help is greatly appreciated...
- general ideas/info on the way iBATIS behaves with JDBC-ODBC bridge and
locks
- maybe I can somehow get Spring to reset the bean?
--
View this message in context: http://www.nabble.com/MS-Access-LDB-locks-using-JDBC-ODBC-bridge-and-iBATIS-tf2017245.html#a5546027
Sent from the iBATIS - User - Java forum at Nabble.com.
Re: MS Access LDB locks using JDBC-ODBC bridge and iBATIS
Posted by Sven Boden <li...@pandora.be>.
You might also consider Kettle ;-) http://kettle.javaforge.com ... but
this is getting pretty OT.
Regards,
Sven
Brandon Goodin wrote:
> I ran across this library and thought it might be useful in dealing with
> your MS Access data imports.
>
> http://jackcess.sourceforge.net/
>
> Brandon Goodin
>
> On 7/29/06, AlexeyG <ag...@z-techcorp.com> wrote:
>>
>>
>> Thanks for your responses!
>>
>> MS Access is used only for data import... admin uploads the MS
>> Access DB
>> and I import records. Successfully imported records get deleted, failed
>> records remain. Admin can then download the DB back and fix failed
>> records.
>>
>> I need that lock released so that I can "compact" the Access DB by
>> launching
>> "access.exe *db path* /compact... Without compacting the Access DB
>> remains
>> the same size even if all but few records are deleted... It is a bit
>> of a
>> pain, but I'm pretty much stuck with that process.. At least I do not
>> have
>> to deal with tables to store failed import data, or write an
>> interface to
>> allow admin to fix it.
>>
>> Sounds like getting a good driver or using JDBC straight up and
>> releasing
>> connections is the way to go... Thanks!
>> --
>> View this message in context:
>> http://www.nabble.com/MS-Access-LDB-locks-using-JDBC-ODBC-bridge-and-iBATIS-tf2017245.html#a5558867
>>
>> Sent from the iBATIS - User - Java forum at Nabble.com.
>>
>>
>
Re: MS Access LDB locks using JDBC-ODBC bridge and iBATIS
Posted by Brandon Goodin <br...@gmail.com>.
I ran across this library and thought it might be useful in dealing with
your MS Access data imports.
http://jackcess.sourceforge.net/
Brandon Goodin
On 7/29/06, AlexeyG <ag...@z-techcorp.com> wrote:
>
>
> Thanks for your responses!
>
> MS Access is used only for data import... admin uploads the MS Access DB
> and I import records. Successfully imported records get deleted, failed
> records remain. Admin can then download the DB back and fix failed
> records.
>
> I need that lock released so that I can "compact" the Access DB by
> launching
> "access.exe *db path* /compact... Without compacting the Access DB
> remains
> the same size even if all but few records are deleted... It is a bit of a
> pain, but I'm pretty much stuck with that process.. At least I do not
> have
> to deal with tables to store failed import data, or write an interface to
> allow admin to fix it.
>
> Sounds like getting a good driver or using JDBC straight up and releasing
> connections is the way to go... Thanks!
> --
> View this message in context:
> http://www.nabble.com/MS-Access-LDB-locks-using-JDBC-ODBC-bridge-and-iBATIS-tf2017245.html#a5558867
> Sent from the iBATIS - User - Java forum at Nabble.com.
>
>
Re: MS Access LDB locks using JDBC-ODBC bridge and iBATIS
Posted by Clinton Begin <cl...@gmail.com>.
If you're using Spring, the connections are pooled and likely never closed.
You'll need to disable pooling. I think you can do that by using their
DriverManagerDataSource implementation (IIRC).
Cheers,
Clinton
On 7/30/06, Gwyn Evans <gw...@gmail.com> wrote:
>
> Well, I'd still try & take a look to see if there's anything you can
> do to ensure that all connections are closed, as there's no suggestion
> that the bridge is not working for you in any other way.
>
> /Gwyn
>
> On 29/07/06, AlexeyG <ag...@z-techcorp.com> wrote:
> >
> > Thanks for your responses!
> >
> > MS Access is used only for data import... admin uploads the MS Access
> DB
> > and I import records. Successfully imported records get deleted, failed
> > records remain. Admin can then download the DB back and fix failed
> records.
> >
> > I need that lock released so that I can "compact" the Access DB by
> launching
> > "access.exe *db path* /compact... Without compacting the Access DB
> remains
> > the same size even if all but few records are deleted... It is a bit of
> a
> > pain, but I'm pretty much stuck with that process.. At least I do not
> have
> > to deal with tables to store failed import data, or write an interface
> to
> > allow admin to fix it.
> >
> > Sounds like getting a good driver or using JDBC straight up and
> releasing
> > connections is the way to go... Thanks!
> > --
> > View this message in context:
> http://www.nabble.com/MS-Access-LDB-locks-using-JDBC-ODBC-bridge-and-iBATIS-tf2017245.html#a5558867
> > Sent from the iBATIS - User - Java forum at Nabble.com.
> >
> >
>
Re: MS Access LDB locks using JDBC-ODBC bridge and iBATIS
Posted by Gwyn Evans <gw...@gmail.com>.
Well, I'd still try & take a look to see if there's anything you can
do to ensure that all connections are closed, as there's no suggestion
that the bridge is not working for you in any other way.
/Gwyn
On 29/07/06, AlexeyG <ag...@z-techcorp.com> wrote:
>
> Thanks for your responses!
>
> MS Access is used only for data import... admin uploads the MS Access DB
> and I import records. Successfully imported records get deleted, failed
> records remain. Admin can then download the DB back and fix failed records.
>
> I need that lock released so that I can "compact" the Access DB by launching
> "access.exe *db path* /compact... Without compacting the Access DB remains
> the same size even if all but few records are deleted... It is a bit of a
> pain, but I'm pretty much stuck with that process.. At least I do not have
> to deal with tables to store failed import data, or write an interface to
> allow admin to fix it.
>
> Sounds like getting a good driver or using JDBC straight up and releasing
> connections is the way to go... Thanks!
> --
> View this message in context: http://www.nabble.com/MS-Access-LDB-locks-using-JDBC-ODBC-bridge-and-iBATIS-tf2017245.html#a5558867
> Sent from the iBATIS - User - Java forum at Nabble.com.
>
>
Re: MS Access LDB locks using JDBC-ODBC bridge and iBATIS
Posted by AlexeyG <ag...@z-techcorp.com>.
Thanks for your responses!
MS Access is used only for data import... admin uploads the MS Access DB
and I import records. Successfully imported records get deleted, failed
records remain. Admin can then download the DB back and fix failed records.
I need that lock released so that I can "compact" the Access DB by launching
"access.exe *db path* /compact... Without compacting the Access DB remains
the same size even if all but few records are deleted... It is a bit of a
pain, but I'm pretty much stuck with that process.. At least I do not have
to deal with tables to store failed import data, or write an interface to
allow admin to fix it.
Sounds like getting a good driver or using JDBC straight up and releasing
connections is the way to go... Thanks!
--
View this message in context: http://www.nabble.com/MS-Access-LDB-locks-using-JDBC-ODBC-bridge-and-iBATIS-tf2017245.html#a5558867
Sent from the iBATIS - User - Java forum at Nabble.com.