[
https://issues.apache.org/jira/browse/VFS-374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Eckenfels updated VFS-374:
--------------------------------
Fix Version/s: (was: Nightly Builds)
2.1
> Incorrect lazy initialization of static field
> org.apache.commons.vfs2.util.Messages.resources in
> org.apache.commons.vfs2.util.Messages.findMessage(String)
> ----------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: VFS-374
> URL: https://issues.apache.org/jira/browse/VFS-374
> Project: Commons VFS
> Issue Type: Bug
> Affects Versions: 2.0
> Environment: Apache Maven 3.0.3 (r1075438; 2011-02-28 12:31:09-0500)
> Maven home: C:\Java\apache-maven-3.0.3\bin\..
> Java version: 1.6.0_29, vendor: Sun Microsystems Inc.
> Java home: C:\Program Files\Java\jdk1.6.0_29\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
> Reporter: Gary Gregory
> Fix For: 2.1
>
>
> FindBugs Eclipse plugin reports:
> Bug: Incorrect lazy initialization of static field
> org.apache.commons.vfs2.util.Messages.resources in
> org.apache.commons.vfs2.util.Messages.findMessage(String)
> This method contains an unsynchronized lazy initialization of a non-volatile
> static field. Because the compiler or processor may reorder instructions,
> threads are not guaranteed to see a completely initialized object, if the
> method can be called by multiple threads. You can make the field volatile to
> correct the problem. For more information, see the Java Memory Model web
> site.
> Confidence: Normal, Rank: Troubling (14)
> Pattern: LI_LAZY_INIT_STATIC
> Type: LI, Category: MT_CORRECTNESS (Multithreaded correctness)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
