You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@commons.apache.org by "Matt Sicker (JIRA)" <ji...@apache.org> on 2017/03/04 20:19:45 UTC

[jira] [Closed] (POOL-320) Use more efficient stack walking mechanisms for usage tracking

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

Matt Sicker closed POOL-320.
----------------------------
       Resolution: Fixed
    Fix Version/s: 2.4.3

Added in subversion revision 1785520 in trunk.

> Use more efficient stack walking mechanisms for usage tracking
> --------------------------------------------------------------
>
>                 Key: POOL-320
>                 URL: https://issues.apache.org/jira/browse/POOL-320
>             Project: Commons Pool
>          Issue Type: Improvement
>    Affects Versions: 2.4.2
>            Reporter: Matt Sicker
>            Assignee: Matt Sicker
>             Fix For: 2.4.3
>
>
> When usage tracking is enabled, pooled object users are discovered by creating an exception. This is slower than optimal which could be done via various strategies such as a SecurityManager, reflection on the internal Reflection class, or for Java 9 users, the new StackWalker API.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)