Hi Phil,
thanks for taking my issue serious.
Phil Steitz wrote:
Thanks again for the feedback. Any other opinions / suggestions on
this are appreciated. I suggest the following compromise, which would
also fix the maxActive exceeded by one issue I discovered with
1.2/1.4-RC1 yesterday:
(*)
Mark, Thomas, thanks for your replies,
Phil Steitz wrote:
On Jan 3, 2008 12:40 PM, Mark Thomas <[EMAIL PROTECTED]> wrote:
Christoph Kutzinski wrote:
- creating a new object means the pool is exhausted which in turn usually means
that we have a high-load situation.
- creation of new objects is
Phil Steitz wrote:
- fully synchronized borrowObject() and returnObject() methods. I've
seen this to be a serious bottleneck when the database is under high
load and another connection needs to be created.
Agreed. Ideas on how to improve this without creating threadsafety
issues would be appr
Hi,
I would like to offer some help, too.
I cannot promise that I can do some actual development work on it, but I
would like to add some comments about some drawbacks (IMHO) in pool 1.3.
Mainly:
- changing GenericObjectPool from LIFO to FIFO strategy from 1.2 to 1.3
I think that a FIFO strate
