Return-Path: X-Original-To: apmail-commons-issues-archive@minotaur.apache.org Delivered-To: apmail-commons-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 32E52C0F3 for ; Fri, 21 Jun 2013 14:42:22 +0000 (UTC) Received: (qmail 50746 invoked by uid 500); 21 Jun 2013 14:42:21 -0000 Delivered-To: apmail-commons-issues-archive@commons.apache.org Received: (qmail 50688 invoked by uid 500); 21 Jun 2013 14:42: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 50665 invoked by uid 99); 21 Jun 2013 14:42:20 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Jun 2013 14:42:20 +0000 Date: Fri, 21 Jun 2013 14:42:20 +0000 (UTC) From: "samir kerroumi (JIRA)" To: issues@commons.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (BEANUTILS-440) MethodUtils.CACHE_METHODS is not accessed in a thread-safe way MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/BEANUTILS-440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13690334#comment-13690334 ] samir kerroumi commented on BEANUTILS-440: ------------------------------------------ there is also another method reading CACHE_METHODS private static void cacheMethod(...) i'm patching it too > MethodUtils.CACHE_METHODS is not accessed in a thread-safe way > -------------------------------------------------------------- > > Key: BEANUTILS-440 > URL: https://issues.apache.org/jira/browse/BEANUTILS-440 > Project: Commons BeanUtils > Issue Type: Bug > Reporter: Sebb > Attachments: BEANUTILS-440.patch > > > MethodUtils.CACHE_METHODS is not accessed in a thread-safe way. > The field is a mutable static field, but is not volatile (nor Atomic) and only write accesses are synchronised. > If one thread writes the field, other reader threads may not see the updates immediately (or ever). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira