Pool evictor Timer cleanup

[Pablo Gra\~na]

Hi there:

I am tracking GC problems in my web app, and I found that the 
GenericKeyedObjectPool evictor keeps the web application context alive. I 
understand that the correct way to handle this is for the pool user to call close().

The problem is that there are some 3rt party apps that use commons-pool and not 
all of them correctly calls close()  (I already reported this to one of them).

I am proposing here a work around for those misbehaving apps: somehow expose the
EvictionTimer._timer, for example, adding a method like this:

    public static synchronized void cancelAll() {
        if (null != _timer) {
            _usageCount = 0;
            _timer.cancel();
            _timer = null;
        }
    }

in EvictionTimer, which will also need to be made public. I tried this in my app 
and it worked fine.

any thoughts?

thanks a lot


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]