I opened a JIRA ticket for the issue:
https://issues.apache.org/jira/browse/POOL-119
Christoph
Henri Yandell wrote:
On Jan 5, 2008 3:39 PM, Mark Thomas <[EMAIL PROTECTED]> wrote:
Phil Steitz wrote:
Yes. It may be ultimately best to make this configurable. If you are
OK with this approach, w
On Jan 5, 2008 3:39 PM, Mark Thomas <[EMAIL PROTECTED]> wrote:
> Phil Steitz wrote:
> > Yes. It may be ultimately best to make this configurable. If you are
> > OK with this approach, what I suggest is that you open a JIRA ticket,
> > attaching a version of your patch that supports configurability
Phil Steitz wrote:
Yes. It may be ultimately best to make this configurable. If you are
OK with this approach, what I suggest is that you open a JIRA ticket,
attaching a version of your patch that supports configurability. Open
the ticket against 1.3 for now but keep the patch as is (i.e. again
> >
> > The 1.2 / 1.4-RC1 code does "recheck" before initiating additional
> > makes - i.e., it will not initiate a makeObject if an idle object has
> > been returned to the pool or if maxActive has been reached. I think I
> > understand your point though, but again it doesn't seem natural to use
