commons-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jason Gordon <>
Subject [pool] GenericKeyedObjectPool with minIdle=1 and active evictor
Date Wed, 13 Mar 2013 16:49:50 GMT
I am confused about the expected behavior with a GenericKeyedObjectPool
with minIdle=1, maxIdle=1, and a running evictor.

Currently when the evictor thread finds an object for a particular key
where validateObject returns false or activateObject returns an exception,
the object is thrown out of the pool but a new object does not seem to be
made with makeObject until someone specifically calls borrowObject.
 However, I thought that if minIdle=1 then if an object is evicted, another
would be created by the evictor to take it's place.

Seemingly, according to below, after eviction new objects would be created:

Is there a workaround to allow one object in the pool for each key and to
have the evictor thread create a new object at the time it invalidates the
existing object?


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message