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

Posted to issues@commons.apache.org by "Phil Steitz (JIRA)" <ji...@apache.org> on 2014/12/31 17:29:14 UTC

[jira] [Closed] (POOL-197) PooledObject: risky init of lastBorrowTime & lastReturnTime

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

Phil Steitz closed POOL-197.
----------------------------

> PooledObject: risky init of lastBorrowTime & lastReturnTime
> -----------------------------------------------------------
>
>                 Key: POOL-197
>                 URL: https://issues.apache.org/jira/browse/POOL-197
>             Project: Commons Pool
>          Issue Type: Bug
>            Reporter: Sebb
>             Fix For: 2.0
>
>
> PooledObject inits lastBorrowTime & lastReturnTime (and createTime) using System.currentTimeMillis().
> As well as being wasteful to call the System method 3 times, it's possible that the clock will change between invocations.
> This could result in getActiveTimeMillis() returning non-zero active time even though the object has never been used.
> Should probably init lastBorrowTime & lastReturnTime from createTime.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)