Return-Path: X-Original-To: apmail-logging-log4net-user-archive@www.apache.org Delivered-To: apmail-logging-log4net-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id AFA3AEBDD for ; Tue, 28 May 2013 14:54:09 +0000 (UTC) Received: (qmail 84007 invoked by uid 500); 28 May 2013 14:54:09 -0000 Delivered-To: apmail-logging-log4net-user-archive@logging.apache.org Received: (qmail 83526 invoked by uid 500); 28 May 2013 14:54:04 -0000 Mailing-List: contact log4net-user-help@logging.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: "Log4NET User" List-Id: Delivered-To: mailing list log4net-user@logging.apache.org Received: (qmail 83472 invoked by uid 99); 28 May 2013 14:54:03 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 May 2013 14:54:03 +0000 X-ASF-Spam-Status: No, hits=0.0 required=5.0 tests=RCVD_IN_DNSWL_NONE,UNPARSEABLE_RELAY X-Spam-Check-By: apache.org Received-SPF: error (athena.apache.org: local policy) Received: from [216.82.243.205] (HELO mail1.bemta8.messagelabs.com) (216.82.243.205) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 May 2013 14:53:56 +0000 Received: from [216.82.241.100:52081] by server-13.bemta-8.messagelabs.com id 50/CD-15464-AD4C4A15; Tue, 28 May 2013 14:53:14 +0000 X-Env-Sender: rajy@michaels.com X-Msg-Ref: server-2.tower-220.messagelabs.com!1369752793!173392!1 X-Originating-IP: [66.142.244.3] X-StarScan-Received: X-StarScan-Version: 6.9.6; banners=michaels.com,-,- X-VirusChecked: Checked Received: (qmail 14110 invoked from network); 28 May 2013 14:53:13 -0000 Received: from mmg.michaels.com (HELO MSIM1) (66.142.244.3) by server-2.tower-220.messagelabs.com with SMTP; 28 May 2013 14:53:13 -0000 Received: from WHVEXHC1.corp.msi.michaels.com ([10.4.31.202]) by MSIM1 with Microsoft SMTPSVC(6.0.3790.4675); Tue, 28 May 2013 09:53:13 -0500 Received: from WHVEXMBX2.corp.msi.michaels.com ([169.254.2.111]) by WHVEXHC1.corp.msi.michaels.com ([10.4.31.202]) with mapi id 14.02.0342.003; Tue, 28 May 2013 09:53:12 -0500 From: Yuvraj Raj To: Log4NET User , Justin Dearing , Dominik Psenner Subject: RE: log4net.dll version 1.2.10.0 (FileSystemWatcher objects) Thread-Topic: log4net.dll version 1.2.10.0 (FileSystemWatcher objects) Thread-Index: Ac5X4vPvfDNnPnN0S6ytY1/88HH3fQBaNWFWAJmKRDA= Date: Tue, 28 May 2013 14:53:12 +0000 Message-ID: <75CF8BEDFEE65A4981D0AEFF27D7D7CE1383F8E3@WHVEXMBX2.corp.msi.michaels.com> References: <75CF8BEDFEE65A4981D0AEFF27D7D7CE1383667C@WHVEXMBX2.corp.msi.michaels.com> <87ppwfp4tk.fsf@v35516.1blu.de> In-Reply-To: <87ppwfp4tk.fsf@v35516.1blu.de> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.4.31.254] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginalArrivalTime: 28 May 2013 14:53:13.0373 (UTC) FILETIME=[1408FCD0:01CE5BB3] X-Virus-Checked: Checked by ClamAV on apache.org Thank you all for the response. I will try testing the newer version 1.2.1= 1.0 and let you know if find any issues. Best Regards, Yuvraj Work: 972 409 5703 | Support: 972 400 0174 | Cell: 469 438 1396 -----Original Message----- From: Stefan Bodewig [mailto:bodewig@apache.org]=20 Sent: Saturday, May 25, 2013 8:28 AM To: Log4NET User Subject: Re: log4net.dll version 1.2.10.0 (FileSystemWatcher objects) Hi Yuvraj On 2013-05-23, Yuvraj Raj wrote: > From the memory dump, They found >2000 instances of=20 > log4net.Config.XmlConfigurator+ConfigureAndWatchHandler and the=20 > FileSystemWatcher objects created that contributed this issue. The=20 > issue is happening due to the fragmentation of Gen2 Heap. The reason=20 > for the fragmentation is the pinned System.IO.Overlapped objects used=20= > by FileSystemWatcher objects. > When looking at the log4net.dll help from Apache web page, we found=20 > the below link for log4net that have bug (LOG4NET-158) in version > 1.2.10.0 saying XmlConfigurator.ConfigureAndWatch() leaks resources if=20= > called multiple times > The issue was fixed in version 1.2.11.0. Please let us know if above=20 > memory issue was related to the bug and it has been resolved in the=20 > next release. To be honest, we don't know for sure. Without knowing exactly how the man= y instances have been created in your case, it is hard to answer. If you = had been invoking ConfigureAndWatch multiple times, then yes, this is like= ly fixed now. BTW, 1.2.11 has been released something like 20 months ago, so you may wan= t to give it a try. Stefan __________________________________________________________________________= ___ Scanned by IBM Email Security Management Services powered by MessageLabs. = For more information please visit http://www-935.ibm.com/services/us/index= .wss/offerfamily/iss/a1026954 __________________________________________________________________________= ___ __________________________________________________________________________= ___ Scanned by IBM Email Security Management Services powered by MessageLabs. = For more information please visit http://www-935.ibm.com/services/us/index= .wss/offerfamily/iss/a1026954 __________________________________________________________________________= ___