Re: [dbcp] PoolableConnectionFactory validation and
synchronized methods
Hello Brad,
There is indeed no technical reason why PoolableConnectionFactory should
be
synchronized but I didn't want to include this change in 1.1.
First it should be tested by multiple people / multiple database systems
to
see how th
Todd,
Your issue is a different from the performance increase Brad proposes.
He is talking about a BasicDataSource pool like system with
PoolableConnectionFactory and a GenericObjectPool.
This pool is already optimized, the GenericKeyedObjectPool isn't.
I don't agree with your statement that the
Hello Brad,
There is indeed no technical reason why PoolableConnectionFactory should be
synchronized but I didn't want to include this change in 1.1.
First it should be tested by multiple people / multiple database systems to
see how the system reacts in the real world.
There is indeed a good c
] PoolableConnectionFactory validation and synchronized
methods
Hello Dirk,
Well, we are trying to get as much concurrency out of our application as we
can (uPortal running on Tomcat). Seems that allowing concurrent connections
to the database should help performance, and might allow your code to
Hello Dirk,
Well, we are trying to get as much concurrency out of our application as we can
(uPortal running on Tomcat). Seems that allowing concurrent connections to the
database should help performance, and might allow your code to perform well enough
that it exposes a bottleneck in the data
