Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <dev@tomcat.apache.org>
Date: Sat, 2 Oct 2010 16:10:50 -0400 (EDT)
Message-Id: <201010022010.o92KAoU8015603@thor.apache.org>
From: bugzilla@apache.org
To: dev@tomcat.apache.org
Subject: DO NOT REPLY [Bug 49985] Lazy initialization without any
 synchronization - data race in AstInteger, AstFloatingPoint, AstString
In-Reply-To: <bug-49985-78@https.issues.apache.org/bugzilla/>
References: <bug-49985-78@https.issues.apache.org/bugzilla/>
Auto-Submitted: auto-generated
Content-Type: text/plain; charset="UTF-8"
MIME-Version: 1.0

https://issues.apache.org/bugzilla/show_bug.cgi?id=49985

--- Comment #11 from Kostya Serebryany <konstantin.s.serebryany@gmail.com> 2010-10-02 16:10:45 EDT ---
(In reply to comment #10)
> Fixed in trunk (will be in 7.0.3 onwards) and proposed for 6.0.x.
> 
> There are many places were static analysis 
This is why we use dynamic analysis :) 
We are experimenting with ThreadSanitizer for Java (search for it if curious). 
Not something we can offer to users yet, but already 'sort of works for us'. 

> incorrectly reports thread safety
> issues in the Tomcat code base. Bug reports that look like copy and pasted
> output from these tools tends to get ignored / resolved as invalid. In this
> case it took a close inspection of the EL parser to spot the place where these
> objects were cached to confirm this as a potential issue.
> 
> If you have done the analysis that demonstrates that there really is an issue
> it saves a lot of time all round if you include that in the initial bug report.
Agree.

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

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