commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Sicker (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (POOL-320) Use more efficient stack walking mechanisms for usage tracking
Date Sat, 04 Mar 2017 20:19:45 GMT

     [ 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)

Mime
View raw message