commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Thomas (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (POOL-137) Inconsistent synchronization in GenericObjectPool; constant fields should be final
Date Mon, 18 May 2009 20:17:45 GMT

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

Mark Thomas resolved POOL-137.
------------------------------

       Resolution: Fixed
    Fix Version/s: 1.5

I have fixed the sync issues as best I can even though I am not a huge fan of my solution.
I think the whole sync strategy needs to be re-thought for 2.0. I'll write up something for
the dev list when we reach that point.

> Inconsistent synchronization in GenericObjectPool; constant fields should be final
> ----------------------------------------------------------------------------------
>
>                 Key: POOL-137
>                 URL: https://issues.apache.org/jira/browse/POOL-137
>             Project: Commons Pool
>          Issue Type: Bug
>            Reporter: Sebb
>             Fix For: 1.5
>
>
> _whenExhaustedAction is not always accessed using synchronization.
> The private static Latch class appears to be used across threads, but has no synchronization.
> The static class Config contains several fields which appear to be used as constants,
however the fields are not final.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message