Hi David,
David Hoffer wrote at Donnerstag, 10. September 2009 18:07:
We have upgraded commons-configuration to version 1.6 (was 1.1) and
now I get an this error when we mock something using EasyMock that is
hard coded to use commons-configuration to read conf data from
file(s).
Watching the source code, it seems to me the implementation of
Generic{Keyed}ObjectPool is thread-safe.
So what is the need of PoolUtils.synchronizedPool ?
Can someone explain me ? I can't find the answer in the docs :(
--
View this message in context:
Emanuele Gheradini wrote:
Watching the source code, it seems to me the implementation of
Generic{Keyed}ObjectPool is thread-safe.
So what is the need of PoolUtils.synchronizedPool ?
Can someone explain me ? I can't find the answer in the docs :(
Look at the JavaDocs.
Mark
Yeah, I found it...our build guy is trying to figure out why we still have a
non 1.6 compatable override in one of our jars.
Dave
- sent via G1
On Sep 11, 2009 12:24 AM, Jörg Schaible joerg.schai...@gmx.de wrote:
Hi David,
David Hoffer wrote at Donnerstag, 10. September 2009 18:07:
We have
all,
we are running some performance tests and in one of the test script, i am
tracking the time it takes to check out a connection from the pool.
times in milliseconds:
9, 16, 2, 127, 9, 145
the question is why would it vary so much? and how do i trouble shoot as i why
it took so much time
daniel steel wrote:
all,
we are running some performance tests and in one of the test script, i am
tracking the time it takes to check out a connection from the pool.
times in milliseconds:
9, 16, 2, 127, 9, 145
the question is why would it vary so much? and how do i trouble shoot as
Dari milis sebelah
Shalat Jum'at yang mengubah sejarah Amerika
INILAH.COM http://inilah.com/, Washington - Amerika Serikat di bawah
Presiden Barack Obama kembali ingin menekankan sikap bersahabatnya dengan
dunia Islam. Bahkan untuk pertama kalinya, halaman Capitol Hill, tempat
Obama dilantik
