You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@empire-db.apache.org by "Rainer Döbele (JIRA)" <em...@incubator.apache.org> on 2013/02/04 15:08:13 UTC
[jira] [Closed] (EMPIREDB-49) Non-thread-safe counters
[ https://issues.apache.org/jira/browse/EMPIREDB-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rainer Döbele closed EMPIREDB-49.
---------------------------------
Cleanup of unclosed issues.
> 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-incubating
>
>
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira