Hi Chad,
Didn't get your emails until this morning -- are you experiencing the
same problems that I was talking about? Basically, it seems like a new
connection pool is getting set up after every JNDI lookup (which I'd
basically like to do every time I run a query). If I hold on to the
same da
this context?
TIA,
Ozgur.
> -Original Message-
> From: Scott Jones [mailto:[EMAIL PROTECTED]]
> Sent: Monday, April 22, 2002 10:09 AM
> To: Tomcat Users List
> Cc: Chad Johnson
> Subject: Re: DBCP Database Connection pooling in TC4
>
>
> Hi Chad,
>
>
Hello Scott,
There is another connection pool located in commons-sandbox/jdbc2pool
that behaves as you expect, multiple lookups of the same pool will NOT
reset the pool. Jdbc2pool is written to use a ConnectionPoolDataSource
as the backend providing the connections. It does have an adapter
pack
Hi John,
Ah, very nice. That's exactly what I was looking for... I don't
actually understand why you'd ever want the pool to get reset.
Before, I actually had JDBC Connection Pooling set up using the
bitmechanic jdbcpool (http://www.bitmechanic.com/projects/jdbcpool/).
However, I want to us
Ozgur Sahoglu wrote:
>
> Hi,
>
> What is the difference between javax.sql.DataSource and
> javax.sql.ConnectionPoolDataSource interfaces?
A DataSource is meant to be used by an application. It could be written
by the jdbc driver as a way to provide physical db connections. It is
also the inte