Hi,
https://issues.apache.org/jira/browse/POOL-119 "GenericObjectPool:
Provide option to create new objects serial"
I had created this issue long ago, but as I have currently no interest
in commons-pool anymore and no one else seems to care about the issue I
describe there: Is it okay POOL-1
> > Not having thought this through all the way, I was thinking about an
> > integer property that could take one of four values
> > "BORROWED" - a ghost in the pool snapshot
> > "IDLE" - in the pool, OK to borrow
> > "DEAD" - in the pool, marked for eviction
> > "VALIDATING" - in the pool, being
Phil Steitz wrote:
> 3) when to do _factory.destroyObject - can't do this is the
> mid-section because borrowObject could jump in and grab the destroyed
> object. Need some way to prevent that, maybe by locking / marking the
> ObjectTimeStampPair.
That could be done after the second synch
Hi Phil,
Phil Steitz wrote:
Thanks, Christoph
On Sat, Mar 1, 2008 at 4:21 AM, Christoph Kutzinski <[EMAIL PROTECTED]> wrote:
As the 'inversed' locking order in evict() is obviously the source of
the problems, I would try to avoid calling any _factory methods while
holding
As the 'inversed' locking order in evict() is obviously the source of
the problems, I would try to avoid calling any _factory methods while
holding the 'this' lock.
I thinking about something like this:
public void evict() {
CursorableLinkedList tmpPool;
Collection connsToEvict = new Array
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
Phil Steitz wrote:
If you are really worried about the cost of object creation then you can
configure the pool to create all the objects at start-up and block until a
free object is available.
That is unfortunately not possible under our current configuration as we
have set up our application
Hi,
sorry for the late reply, but I've been very busy in the last weeks.
I still wanted to make some comments on the changes to the synchronization in
GenericObjectPool (and that like) - not sure which JIRA number refers to that.
I think one of the few good things about the strong synchronizatio
Hi,
> On Dec 2, 2007 2:24 PM, <[EMAIL PROTECTED]> wrote:
> > 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.
> > >
That's not entirely true
http://java.sun.com/j2se/1.3/download.html
"On Solaris 8 - J2SE 1.3.1 is continuing in the Sun End of Life (EOL) process.
The EOL transition period began Oct 25, 2004 and will continue until the the
end of the Solaris 8 five year Vintage Support Period."
;-)
> Another
10 matches
Mail list logo
