Hi,
I would like to download jdbc-pool library. However, I am unable to find the
library in jakarata.apache.org.
Can anybody tell me where from I can download this file?

Regards,
Narendra

>
>  ---------- Forwarded message ----------
> From: Eric B. <ebe...@hotmail.com>
> Date: Tue, Jun 23, 2009 at 10:13 AM
> Subject: Re: dbcp pool evictor deadlock?
> To: dev@tomcat.apache.org
>
>
> "Mark Thomas" <ma...@apache.org> wrote in message
> news:4a40e12c.2070...@apache.org...
> > Narendra Sarkar wrote:
> >> Hi,
> >> We have a multi threaded environment. We have noticed that thread blocks
> >> for
> >> 10 to 20 minutes due DBCP getConnection method call. Then, we
> >> investigated
> >> the source code of DBCP(commons-dbcp-1.2.1-PII.jar) and noticed that
> >> createConnection method is synchronized. This problem occur more
> >> frequently
> >> when we have lower value of MaxIdleConnection parameter. After
> increasing
> >> the value of MaxIdleConnection parameter, frequency of blocking get
> >> reduced.
> >> We then replaced DBCP connection pooling with Oracle Connection pooling
> >> (ojdbc14.jar) and never encountered blocking issue.
> >>
> >> I think the issue is with that createConnection method of DBCP
> >> synchronization. We have taken Thread dump to do above analysis.
> >
> > Yep, known issues with commons-pool. Should be fixed in 1.5.1. Trunk has
> > been updated. Proposed for 6.0.x and 5.5.x. Alternatively, there is the
> > new JDBC pool module.
>
> I'm a little confused now.   Filip pointed me to the jdbp-1.0.5 package.
>  Is
> that just repackaged versions of dbcp 1.2.2/pool 1.5?  If not, what
> versions
> of dbcp/pool are contained within there?
>
> If the fix in commons-pool is in 1.5.1, am I still expecting concurrency
> problems if upgrading 1.5?  What would be the best move?
>
> Thanks,
>
> Eric
>
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: dev-h...@tomcat.apache.org
>
>
>

Reply via email to