[
https://issues.apache.org/jira/browse/POOL-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16668292#comment-16668292
]
Mark Thomas commented on POOL-355:
----------------------------------
I'd lean towards a WONTFIX for this. The maximum value of numActive on its own
is of little to no use for sizing the pool as, to get correct sizing, you need
to look at the value of numActive over time along side the application's
requirements. numActive is already exposed over JMX (along with a bunch of
other values that might be useful) and can be accessed via the monitoring tool
of choice.
We currently have StatsStore providing means for active, idle and wait times. I
did consider if something similar would be possible for numActive but, unlike
those times, there isn't an obvious trigger for recording individual values of
numActive that would provide meaningful 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)
