Re: JDBC AbandonedObjectPool and PoolableConnectionFactory

2003-09-28 Thread Dirk Verbeeck
You can remove the synchronization of the validateObject method in PoolableConnectionFactory but be carefull. If the query is slow because the database is overloaded then allowing more validationQueries will increase the problem. For the next release I'm thinking about monitoring SQLExceptions t

Re: JDBC AbandonedObjectPool and PoolableConnectionFactory

2003-09-28 Thread Glenn Nielsen
This should be fixed in CVS now. Glenn John McNally wrote: yes that looks like a correct observation. The synchronization scope could be reduced. john mcnally On Wed, 2003-09-24 at 14:47, Brad Johnson wrote: Hello, I noticed the latest commit to AbandonedObjectPool.java in the Jakarta Commons

Re: JDBC AbandonedObjectPool and PoolableConnectionFactory

2003-09-26 Thread John McNally
yes that looks like a correct observation. The synchronization scope could be reduced. john mcnally On Wed, 2003-09-24 at 14:47, Brad Johnson wrote: > Hello, > > I noticed the latest commit to AbandonedObjectPool.java in the Jakarta Commons DBCP > project. The changes seem to fix some thread bl

JDBC AbandonedObjectPool and PoolableConnectionFactory

2003-09-24 Thread Brad Johnson
Hello, I noticed the latest commit to AbandonedObjectPool.java in the Jakarta Commons DBCP project. The changes seem to fix some thread blocking that I have observed lately on our Tomcat uPortal app. I tried out the new nightly (9/24/03) today, and I think another point of thread contention ha