Mailing-List: contact dev-help@groovy.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@groovy.incubator.apache.org
Subject: Re: Groovy category throwing MissingMethodException and
 MissingPropertyException when using multiple threads
To: dev@groovy.incubator.apache.org, users@groovy.incubator.apache.org
References: 
 <CAJ4jX6jWc4BbotTB3jkKyw-ycgFm6bCqWqNQoHGAaxny8pDGqA@mail.gmail.com>
 <56311C00.9020702@gmx.net>
 <1BCD07F2-703A-4EA8-B5C9-FBC5B99DC116@cs.vassar.edu>
From: Jochen Theodorou <blackdrag@gmx.org>
Message-ID: <563278FA.8070404@gmx.org>
Date: Thu, 29 Oct 2015 20:52:26 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <1BCD07F2-703A-4EA8-B5C9-FBC5B99DC116@cs.vassar.edu>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

On 29.10.2015 11:48, Suderman Keith wrote:
> There are (at least) two race conditions in GroovyCategorySupport.java
> that would explain the intermittent and hard to reproduce bugs.
>
> I was hoping to submit this as my first official pull request to the
> Groovy project, but gradle has different ideas…
>
> However, the offending code is in on lines 75-76 and 99-100 where
> atomicCategoryUsageCounter is used non-atomically. If no one beats me to
> it I will submit a PR once I puzzle out why ./gradlew test is failing
> for me.

Can you explain the non-atomic usage and why it leads to a problem here?

bye blackdrag