You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@commons.apache.org by bu...@apache.org on 2003/02/12 19:10:54 UTC

DO NOT REPLY [Bug 17015] New: - GenericObjectPool.invalidateObject() doesn't work with AbandonedObjectPool

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17015>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17015

GenericObjectPool.invalidateObject() doesn't work with AbandonedObjectPool 

           Summary: GenericObjectPool.invalidateObject() doesn't work with
                    AbandonedObjectPool
           Product: Commons
           Version: Nightly Builds
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Dbcp
        AssignedTo: commons-dev@jakarta.apache.org
        ReportedBy: mic@schlund.de


AbandonedObjectPool inherits invalidateObject() from GenericObjectPool, but this
method doesn't update the list of connections in use. Yuck!

AbandonedObjectPool should overwrite the method - possibly like this:


    public synchronized void invalidateObject(Object obj) throws Exception {
        if (config != null && config.getRemoveAbandoned()) {
            trace.remove(obj);
        }
	super.invalidateObject(obj);        
    }

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org