tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject DO NOT REPLY [Bug 49985] Lazy initialization without any synchronization - data race in AstInteger, AstFloatingPoint, AstString
Date Sat, 02 Oct 2010 20:10:50 GMT

--- Comment #11 from Kostya Serebryany <> 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.

Configure bugmail:
------- You are receiving this mail because: -------
You are the assignee for the bug.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message