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

Posted to issues@commons.apache.org by "Jacopo Cappellato (JIRA)" <ji...@apache.org> on 2014/10/05 08:03:33 UTC

[jira] [Updated] (POOL-279) Thread concurrency issue in DefaultPooledObject.getIdleTimeMillis()

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

Jacopo Cappellato updated POOL-279:
-----------------------------------
    Attachment: POOL-279.patch

> Thread concurrency issue in DefaultPooledObject.getIdleTimeMillis()
> -------------------------------------------------------------------
>
>                 Key: POOL-279
>                 URL: https://issues.apache.org/jira/browse/POOL-279
>             Project: Commons Pool
>          Issue Type: Bug
>    Affects Versions: 2.0
>            Reporter: Jacopo Cappellato
>            Priority: Minor
>         Attachments: POOL-279.patch
>
>
> Under unlucky thread concurrency the getIdleTimeMillis() method of DefaultPooledObject can return a negative value.
> I have attached a Junit test that fails most of the times and a simple fix, that doesn't use synchronization: with this fix the Junit test always succeed.



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