commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Samira Tasharofi (Created) (JIRA)" <j...@apache.org>
Subject [jira] [Created] (POOL-193) It is safer to make org.apache.commons.pool2.impl.GenericObjectPool.evictor volatile
Date Tue, 29 Nov 2011 19:33:40 GMT
It is safer to make org.apache.commons.pool2.impl.GenericObjectPool.evictor volatile
------------------------------------------------------------------------------------

                 Key: POOL-193
                 URL: https://issues.apache.org/jira/browse/POOL-193
             Project: Commons Pool
          Issue Type: Bug
    Affects Versions: Nightly Builds
         Environment: Platform: All
            Reporter: Samira Tasharofi


A field of [org.apache.commons.pool2.impl.GenericObjectPool<T>|http://svn.apache.org/repos/asf/!svn/bc/1206499/commons/proper/pool/trunk/src/java/org/apache/commons/pool2/impl/GenericObjectPool.java]
might need to be synchronized. Field {{org.apache.commons.pool2.impl.GenericObjectPool.evictor}}
is read and written in method {{org.apache.commons.pool2.impl.GenericObjectPool.startEvictor(long)}},
which might be called by multiple threads concurrently. Is there a possibility that {{org.apache.commons.pool2.impl.GenericObjectPool.startEvictor(long)}}
gets invoked concurrently? Would it be safer to make {{org.apache.commons.pool2.impl.GenericObjectPool.evictor}}
{{volatile}}?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message