Grouper Developers Forum

[Chris Hyzer <>]

Well, grouper and the subject api ship with it working, so people don't have 
to worry.

> I actually would argue the point of the pool is to do that for you.

Right, I guess.  If the pool verifies the connection on checkout or checkin, 
then it can do it for you.  However, that can be a lot of overhead.  So if 
you check the connection max every minute, that doesn't have as much 
overhead, but then if you have a bad connection, then you could get errors 
for a minute.  I think it is nice to be able to check every minute, and be 
able to take connections out of the pool when there is an exception... but 
anyways, we are getting into the weeds and I think we both agree that if 
there is one that works that we can get rid of dbcp...

Thanks,
Chris



-----Original Message-----
From: Cantor, Scott 
[mailto:]
 
Sent: Thursday, September 22, 2011 4:01 PM
To: Chris Hyzer; Tom Zeller
Cc: Grouper Dev
Subject: Re: [grouper-dev] remind me : java 1.6 or 1.5 ?

On 9/22/11 3:55 PM, "Chris Hyzer" 
<>
 wrote:

>The history is, at the previous hibernate upgrade (2008?  2009?),
>hibernate stopped shipping with dbcp, and it still doesn't.  So we
>switched it to c3p0.  I agree that both work fine, I think c3p0 has more
>useful options than dbcp, but I don't remember the specifics.

I was actually saying that in my experience c3p0 doesn't work at all. (The
IdP ships with it, I had to switch to container managed connections to get
away from it.) If it works for others, that's nice.

>  There is a pooling interface to implement where any pool can be used.
>Its not just a datasource since I think it is useful to be able to remove
>connections from the pool if there is an error without having to test it
>on every checkout or checking, but maybe that is just me :)

I actually would argue the point of the pool is to do that for you.

-- Scott