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/10/05 18:50:35 UTC

[jira] [Resolved] (POOL-275) BaseProxyHandler.pooledObject is not volatile or synch, so is not guaranteed to be safely published.

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

Phil Steitz resolved POOL-275.
------------------------------
       Resolution: Fixed
    Fix Version/s: 2.3

Fixed in r1629504.

> BaseProxyHandler.pooledObject is not volatile or synch, so is not guaranteed to be safely published.
> ----------------------------------------------------------------------------------------------------
>
>                 Key: POOL-275
>                 URL: https://issues.apache.org/jira/browse/POOL-275
>             Project: Commons Pool
>          Issue Type: Bug
>            Reporter: Sebb
>             Fix For: 2.3
>
>
> BaseProxyHandler.pooledObject is not volatile or synch, so is not guaranteed to be safely published.
> The class Javadoc does not state whether it is intended to be thread-safe or not, but I would expect the class might be called from multiple threads.
> One solution would be to make the field volatile.



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