----------------------------------------------------------------
BEFORE YOU POST, search the faq at <http://java.apache.org/faq/>
WHEN YOU POST, include all relevant version numbers, log files,
and configuration files. Don't make us guess your problem!!!
----------------------------------------------------------------
Hi!
In fact, my experience is that a connectionpool is a must if
You want it all to work smoothly and with speed.
Check out the turbine project. You will find a pool there.
//OLAS
Lars Fastrup skrev:
> ----------------------------------------------------------------
> BEFORE YOU POST, search the faq at <http://java.apache.org/faq/>
> WHEN YOU POST, include all relevant version numbers, log files,
> and configuration files. Don't make us guess your problem!!!
> ----------------------------------------------------------------
>
> Hi Cameron,
>
> connection pooling sounds like a really good idea! Can you recommend a good
> standard pooling library? What do you use yourself?
>
> thx
> Lars Fastrup
>
> "Riley, Cameron" wrote:
>
> > ----------------------------------------------------------------
> > BEFORE YOU POST, search the faq at <http://java.apache.org/faq/>
> > WHEN YOU POST, include all relevant version numbers, log files,
> > and configuration files. Don't make us guess your problem!!!
> > ----------------------------------------------------------------
> >
> > >Moral of the story? Don't bother with JDBC-ODBC and Access with JDK 1.2
> >
> > We created a small commercial application that used Access as the database.
> > It has a low volume of data and few concurrent db connections. Added to ease
> > of administration and low cost we chose Access. The application has not once
> > crashed during production. It is running as a service on an NT box with
> > JServ 1.0 on JDK 1.2.
> >
> > We used standard methodologies including connection pooling, prepared
> > statements etc. We also used the standard SUN JDBC:ODBC bridge that comes
> > with the JDK. We had full intentions of upgrading the bridge if it proved
> > unstable. Despite SUN's disclaimers with the JDK documentation the bridge
> > survived testing and has worked fine in production. In the right environment
> > and conditions the SUN JDBC:ODBC bridge is fine for a commercial
> > application.
> >
> > Access's main limitation is the 27 concurrent connections, break that limit
> > and it fails. You can hide that limitation to an extent to users via a
> > connection pool. Access in the right environment and within the correct
> > limits, is a viable choice as a low cost and easily managed db for a Servlet
> > Application running on Win32.
> >
> > Cameron Riley
> >
> >
> >
> > --
> > --------------------------------------------------------------
> > Please read the FAQ! <http://java.apache.org/faq/>
> > To subscribe: [EMAIL PROTECTED]
> > To unsubscribe: [EMAIL PROTECTED]
> > Archives and Other: <http://java.apache.org/main/mail.html>
> > Problems?: [EMAIL PROTECTED]
>
> --
> --------------------------------------------------------------
> Please read the FAQ! <http://java.apache.org/faq/>
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Archives and Other: <http://java.apache.org/main/mail.html>
> Problems?: [EMAIL PROTECTED]
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
