commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (POOL-355) Add maxNumActive to pool config
Date Sun, 28 Oct 2018 07:28:00 GMT

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

ASF GitHub Bot commented on POOL-355:
-------------------------------------

GitHub user graben opened a pull request:

    https://github.com/apache/commons-pool/pull/16

    POOL-355: Add maxNumActive flag to pool implementations

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/graben/commons-pool POOL-355

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/commons-pool/pull/16.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #16
    
----
commit f9ed0f3041b2f2668e5683cce0068d6fd3b454fd
Author: Benjamin Graf <benjamin.graf@...>
Date:   2018-10-25T18:04:28Z

    POOL-355: Add maxNumActive flag to pool implementations

----


> 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: Major
>
> 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)

Mime
View raw message