[ 
https://issues.apache.org/jira/browse/POOL-211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13196359#comment-13196359
 ] 

Mark Thomas commented on POOL-211:
----------------------------------

Pool 2 doesn't provide this functionality directly.

The detection of leaked objects should be simpler with Pool2 since all objects 
are tracked and PooledObject contains all the necessary timing and state 
information. Note with Pool1 and DBCP1 this is all done in DBCP. I anticipate 
this moving to Pool2.

Detection of using pooled objects after they have been returned to the pool is 
not currently supported in Pool2 and isn't on the road-map.
                
> Proxy support for pooled objects
> --------------------------------
>
>                 Key: POOL-211
>                 URL: https://issues.apache.org/jira/browse/POOL-211
>             Project: Commons Pool
>          Issue Type: Improvement
>    Affects Versions: 1.6
>            Reporter: Brad Koehn
>              Labels: features, patch
>             Fix For: Nightly Builds
>
>         Attachments: src.jar, test.jar
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> Attached are files and tests that would allow users of commons-pool to 
> interact with a proxy to the pooled object rather than the pooled object 
> itself. This provides two benefits: detection of leaked pooled objects (when 
> returnObject() isn't called) with a stack trace and detection of using pooled 
> objects after they have been returned to the pool. The system provides a 
> delegate which can be placed in front of any ObjectPool, similar to calling 
> Collections.unmodifiableCollection(). Callers do not know that they're 
> working with a proxy rather than the pooled object itself. Implementations 
> are provided to use Java proxies or CGLib (useful when the pooled object 
> doesn't implement an interface). Unit tests are also provided. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to