[
https://issues.apache.org/jira/browse/POOL-355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg resolved POOL-355.
--------------------------------
Resolution: Won't Fix
Oki, closing as won't fix as discussed.
[~graben] No worries, we will not introduce any new dependencies to record
statistics. This is way too much depending on the integration scenario. And as
MarkT pointed out we already expose enough information to allow many different
ways to access the underlying data.
> Add maxNumActive to pool config
> -------------------------------
>
> Key: POOL-355
> URL: https://issues.apache.org/jira/browse/POOL-355
> Project: Commons Pool
> Issue Type: Improvement
> Affects Versions: 2.6.0
> Reporter: Benjamin Graf
> Priority: Minor
>
> To give a pool the "correct" size it is mandatory to know in which bounds
> pooled object size is lying. Therefor a overall count of historical maximum
> of active objects sounds needed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
