empire-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rainer Döbele (JIRA) <empire-db-...@incubator.apache.org>
Subject [jira] Resolved: (EMPIREDB-49) Non-thread-safe counters
Date Wed, 02 Sep 2009 19:56:32 GMT

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

Rainer Döbele resolved EMPIREDB-49.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: empire-db-2.0.6
                   empire-db-2.0.5-incubating

Replaced uses of static int with static AtomicInteger.


> Non-thread-safe counters
> ------------------------
>
>                 Key: EMPIREDB-49
>                 URL: https://issues.apache.org/jira/browse/EMPIREDB-49
>             Project: Empire-DB
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: empire-db-2.0.5-incubating
>            Reporter: Sebb
>            Assignee: Rainer Döbele
>             Fix For: empire-db-2.0.5-incubating, empire-db-2.0.6
>
>
> There are various static counters which are not accessed in a thread-safe way.
> At present, multiple threads may see duplicate numbers.
> The fields involved are:
> DBQuery.queryCount
> DBTable.tableCount
> DBView.viewCount
> All access to these fields needs to be synchronised to ensure uniqueness. Volatile is
not sufficient.
> Perhaps use AtomicInteger variables instead.

-- 
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