We use a c3p0 with Oracle 10g in a system that has about 10k logins a day.  We use testConnectionOnCheckin with testConnectionTestPeriod so that my connections don't have the overhead of test on checkout.  Our connections are used frequently enough that these settings cover any problems with connections and clean them up.  We use 'select 1 from dual' as my test query because it is the simplest query that can be requested from Oracle.  We found a case where having a defined but empty test query caused the pool to go nuts but I'm not sure if this was caused by c3p0 or Spring (pool defined as bean in Spring).

On Fri, Feb 29, 2008 at 4:16 AM, blacksheep <egilmezbilek@gmail.com> wrote:


I am using  c3p0- with Oracle 10g. When db connection is lost, I need
to restart my application because my app can not retrieve a connection from
c3p0. Recently, one of my friend pointed me to testConnectionOnCheckout
confiuration option that is availiable in c3p0.

What's the final verdict about testConnectionOnCheckout on Oracle. I have
read many contradictory statements about it. Some say
c3p0.idleConnectionTestPeriod should be used instead and some say
testConnectionOnCheckout can be used with a fast query set in like
preferredTestQuery=SELECT 1 from dual .

I need your advice.


View this message in context: http://www.nabble.com/testConnectionOnCheckout-tp15753977p15753977.html
Sent from the c3p0 - users mailing list archive at Nabble.com.

This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
c3p0-users mailing list