Return-Path: X-Original-To: apmail-zest-dev-archive@minotaur.apache.org Delivered-To: apmail-zest-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 40AF9186E5 for ; Fri, 27 Nov 2015 02:41:40 +0000 (UTC) Received: (qmail 12045 invoked by uid 500); 27 Nov 2015 02:41:40 -0000 Delivered-To: apmail-zest-dev-archive@zest.apache.org Received: (qmail 12005 invoked by uid 500); 27 Nov 2015 02:41:40 -0000 Mailing-List: contact dev-help@zest.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@zest.apache.org Delivered-To: mailing list dev@zest.apache.org Received: (qmail 11992 invoked by uid 99); 27 Nov 2015 02:41:39 -0000 Received: from Unknown (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 27 Nov 2015 02:41:39 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 5D021C106F for ; Fri, 27 Nov 2015 02:41:39 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.981 X-Spam-Level: ** X-Spam-Status: No, score=2.981 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-us-west.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id 7eALvJVcih-5 for ; Fri, 27 Nov 2015 02:41:34 +0000 (UTC) Received: from mail-lf0-f41.google.com (mail-lf0-f41.google.com [209.85.215.41]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with ESMTPS id 0B30C232D8 for ; Fri, 27 Nov 2015 02:41:34 +0000 (UTC) Received: by lfaz4 with SMTP id z4so114369219lfa.0 for ; Thu, 26 Nov 2015 18:41:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:content-type; bh=tU6HSvkdTrOD7BtD4DVPK9qripfeSggZdnPCWPJRkaw=; b=kvVLJYd7m1sAVUouUAhroCaf5iHiWHI4UAOXeFDrL7udf3y++REDyNybZXGq8RzlGi Pja0gKNgYpSvDl0RdxdGRBpi6LQ3YYng99NFNM27IocuHJadAvsSebmmtX1l1xQ9qJak w8y6/w4rXx28Fk6NWUjddoRBiQ0q7NozxiQSZN4e/3qWs0Wwb5aMGeN5aXHuFP2Jsjw0 R1XJeHV1kvi2PHnF//2+wUJFizkQ9cqDqowYCBJWCt3Zng/iAbQc0h5uonDTCErugvd8 1xknW4HYXwSB7GZrKCl6Xk6Iv/Xd9zvjb8LCWf47CB2b9p199aw/59K8ivEbKVz+ixgO 6YbQ== MIME-Version: 1.0 X-Received: by 10.25.33.4 with SMTP id h4mr15347258lfh.3.1448592092300; Thu, 26 Nov 2015 18:41:32 -0800 (PST) Sender: hedhman@gmail.com Received: by 10.25.18.198 with HTTP; Thu, 26 Nov 2015 18:41:31 -0800 (PST) Received: by 10.25.18.198 with HTTP; Thu, 26 Nov 2015 18:41:31 -0800 (PST) In-Reply-To: References: Date: Fri, 27 Nov 2015 10:41:31 +0800 X-Google-Sender-Auth: gYGcWKv145FvaoLXIjXmfeCwwK0 Message-ID: Subject: ThreadLocal leaks From: Niclas Hedhman To: dev Content-Type: multipart/alternative; boundary=001a113f232c160af605257ca137 --001a113f232c160af605257ca137 Content-Type: text/plain; charset=UTF-8 I just read an interesting article[1], which highlighted something that never really occurred to me. And I think we are guilty of not clearing up the ThreadLocals upon application passivation, and hence leaking massively. This mail is from my mobile, primarily as placeholder for myself, to create a Jira issue about this. [1] http://java.jiderhamn.se/2012/01/29/classloader-leaks-iv-threadlocal-dangers-and-why-threadglobal-may-have-been-a-more-appropriate-name/ Cheers --001a113f232c160af605257ca137--