Return-Path: Delivered-To: apmail-commons-issues-archive@minotaur.apache.org Received: (qmail 98611 invoked from network); 2 Nov 2010 19:00:51 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 2 Nov 2010 19:00:51 -0000 Received: (qmail 48456 invoked by uid 500); 2 Nov 2010 19:01:22 -0000 Delivered-To: apmail-commons-issues-archive@commons.apache.org Received: (qmail 48199 invoked by uid 500); 2 Nov 2010 19:01:21 -0000 Mailing-List: contact issues-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: issues@commons.apache.org Delivered-To: mailing list issues@commons.apache.org Received: (qmail 48191 invoked by uid 99); 2 Nov 2010 19:01:21 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Nov 2010 19:01:21 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Nov 2010 19:01:19 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id oA2J0vXI002282 for ; Tue, 2 Nov 2010 19:00:57 GMT Message-ID: <770075.201501288724457768.JavaMail.jira@thor> Date: Tue, 2 Nov 2010 15:00:57 -0400 (EDT) From: "Sebb (JIRA)" To: issues@commons.apache.org Subject: [jira] Created: (VFS-326) Multi-threading issues MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org Multi-threading issues ---------------------- Key: VFS-326 URL: https://issues.apache.org/jira/browse/VFS-326 Project: Commons VFS Issue Type: Bug Reporter: Sebb Assignee: Sebb SoftRefFilesCache and DefaultFileMonitor use a boolean to communicate between threads, but don't use synchronisation. There is no guarantee that the updated value of the boolean will be seen by the other thread. Adding volatile would fix this. There are also various private instance fields that are not modified after construction. If these were made final, it would improve thread-safety because the fields would then be published correctly across threads. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.