[jira] [Resolved] (POOL-98) Make GenericObjectPool better extensible

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

[jira] [Resolved] (POOL-98) Make GenericObjectPool better extensible

Gilles (Jira)

     [ https://issues.apache.org/jira/browse/POOL-98?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mark Thomas resolved POOL-98.

    Resolution: Fixed
      Assignee: Mark Thomas

Because pool2 retains references to all the objects, not just the idle objects all of the stats listed above were relatively simple to expose.

> Make GenericObjectPool better extensible
> ----------------------------------------
>                 Key: POOL-98
>                 URL: https://issues.apache.org/jira/browse/POOL-98
>             Project: Commons Pool
>          Issue Type: Improvement
>    Affects Versions: 1.3
>            Reporter: Henning Schmiedehausen
>            Assignee: Mark Thomas
>            Priority: Minor
>             Fix For: 2.0
> The current implementation of GenericObjectPool encapsulates the _pool
> object and there is no way to get it directly, which makes some things
> like JMX pool monitoring a bit awkward.
> Would it be possible to either make _pool protected or add a method
> protected Collection getInternalPool() {
>         return _pool;
> }
> or something like that to the GenericObjectPool implementation (and
> probably others, but that is the one that bites me most... :-) )
> This would make extending the GenericObjectPool much easier.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira