Mailing-List: contact empire-db-commits-help@incubator.apache.org;
 run by ezmlm
Precedence: bulk
Reply-To: empire-db-dev@incubator.apache.org
Message-ID: <1825274092.1251921392804.JavaMail.jira@brutus>
Date: Wed, 2 Sep 2009 12:56:32 -0700 (PDT)
From: =?utf-8?Q?Rainer_D=C3=B6bele_=28JIRA=29?=
 <empire-db-dev@incubator.apache.org>
To: empire-db-commits@incubator.apache.org
Subject: [jira] Resolved: (EMPIREDB-49) Non-thread-safe counters
In-Reply-To: <1098519281.1251824913268.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/EMPIREDB-49?page=3Dcom.atlassi=
an.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rainer D=C3=B6bele 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=C3=B6bele
>             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.

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