Hi Attila,
You have made some good points, included you will find a new evictor
implementation with the enhancements you proposed. I didn't want to
use interrupt() so I used a wait/notify technique with synchronized
blocks.
Can you try this version and let me know if it works for you?
Cheers
Di
Hi all,
I've just been through a particularly nasty case of debugging a memory
leak where the evictor thread of GenericObjectPool (as used by DBCP) was
not willing to die and let go of a disposed ClassLoader it held as the
loader of a ProtectionDomain of its inherited SecurityContext. Now, wh
