Return-Path: X-Original-To: apmail-hc-dev-archive@www.apache.org Delivered-To: apmail-hc-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5AF1111836 for ; Sun, 29 Jun 2014 12:08:25 +0000 (UTC) Received: (qmail 6965 invoked by uid 500); 29 Jun 2014 12:08:25 -0000 Delivered-To: apmail-hc-dev-archive@hc.apache.org Received: (qmail 6925 invoked by uid 500); 29 Jun 2014 12:08:25 -0000 Mailing-List: contact dev-help@hc.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "HttpComponents Project" Delivered-To: mailing list dev@hc.apache.org Received: (qmail 6913 invoked by uid 99); 29 Jun 2014 12:08:25 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 29 Jun 2014 12:08:25 +0000 Date: Sun, 29 Jun 2014 12:08:25 +0000 (UTC) From: "Oleg Kalnichevski (JIRA)" To: dev@hc.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (HTTPASYNC-78) AbstractMultiworkerIOReactor.DefaultThreadFactory.COUNT incorrect use of volatile 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/HTTPASYNC-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Kalnichevski resolved HTTPASYNC-78. ---------------------------------------- Resolution: Fixed Fixed in HttpCore trunk and 4.3.x branch. Oleg > AbstractMultiworkerIOReactor.DefaultThreadFactory.COUNT incorrect use of volatile > --------------------------------------------------------------------------------- > > Key: HTTPASYNC-78 > URL: https://issues.apache.org/jira/browse/HTTPASYNC-78 > Project: HttpComponents HttpAsyncClient > Issue Type: Bug > Reporter: Sebb > Priority: Minor > > AbstractMultiworkerIOReactor.DefaultThreadFactory.COUNT is a volatile int which is incremented using ++COUNT. > This is not thread-safe; multiple threads can end up with the same value for COUNT. > Should probably use AtomicInt instead -- This message was sent by Atlassian JIRA (v6.2#6252) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org For additional commands, e-mail: dev-help@hc.apache.org