Return-Path: Delivered-To: apmail-commons-issues-archive@minotaur.apache.org Received: (qmail 38595 invoked from network); 16 Apr 2010 07:47:51 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 16 Apr 2010 07:47:51 -0000 Received: (qmail 68959 invoked by uid 500); 16 Apr 2010 07:47:50 -0000 Delivered-To: apmail-commons-issues-archive@commons.apache.org Received: (qmail 68650 invoked by uid 500); 16 Apr 2010 07:47:50 -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 68640 invoked by uid 99); 16 Apr 2010 07:47:49 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 Apr 2010 07:47:49 +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; Fri, 16 Apr 2010 07:47:46 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o3G7lPBt003905 for ; Fri, 16 Apr 2010 03:47:25 -0400 (EDT) Message-ID: <25993952.5561271404045474.JavaMail.jira@thor> Date: Fri, 16 Apr 2010 03:47:25 -0400 (EDT) From: "Oscar Gonzalez (JIRA)" To: issues@commons.apache.org Subject: [jira] Created: (FILEUPLOAD-181) finalize method substitution 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 finalize method substitution ---------------------------- Key: FILEUPLOAD-181 URL: https://issues.apache.org/jira/browse/FILEUPLOAD-181 Project: Commons FileUpload Issue Type: Improvement Reporter: Oscar Gonzalez As some java.sun.com articles recommends, the finalize method should be substituted to improve memory management. In heavy load environment, with many upload executions, the use of finalize method may cause OutOfMemoryErrors because of low priority of FinalizerThread. See http://www.fasterj.com/articles/finalizer1.shtml and http://www.fasterj.com/articles/finalizer2.shtml See http://java.sun.com/developer/technicalArticles/javase/finalization/ to see an alternative -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira