commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcos Sanz (JIRA)" <j...@apache.org>
Subject [jira] Updated: (POOL-101) BaseObjectPool does not provide atomicity for closed-Operations
Date Fri, 13 Apr 2007 13:24:15 GMT

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

Marcos Sanz updated POOL-101:
-----------------------------

    Description: 
Though the "closed" field has been declared volatile in the abstract class BaseObjectPool,
atomic operations are not guaranteed. Thus, the code

    public void close() throws Exception {
        assertOpen();
        closed = true;
    }

is broken. I've marked the issue as minor priority, since the semantic consequences are not
very far-reaching (in the worst case, the pool can be closed twice), but the error could be
potentiated if exploited further.

  was:
Though the "closed" field has been declared volatile in the abstract class BaseObjectPool,
atomic operations are not guaranteed. Thus, the code



> BaseObjectPool does not provide atomicity for closed-Operations
> ---------------------------------------------------------------
>
>                 Key: POOL-101
>                 URL: https://issues.apache.org/jira/browse/POOL-101
>             Project: Commons Pool
>          Issue Type: Bug
>    Affects Versions: 1.3
>            Reporter: Marcos Sanz
>            Priority: Minor
>
> Though the "closed" field has been declared volatile in the abstract class BaseObjectPool,
atomic operations are not guaranteed. Thus, the code
>     public void close() throws Exception {
>         assertOpen();
>         closed = true;
>     }
> is broken. I've marked the issue as minor priority, since the semantic consequences are
not very far-reaching (in the worst case, the pool can be closed twice), but the error could
be potentiated if exploited further.

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


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message