Return-Path: Delivered-To: apmail-geronimo-user-archive@www.apache.org Received: (qmail 30985 invoked from network); 14 Sep 2009 15:01:50 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 14 Sep 2009 15:01:50 -0000 Received: (qmail 93106 invoked by uid 500); 14 Sep 2009 15:01:48 -0000 Delivered-To: apmail-geronimo-user-archive@geronimo.apache.org Received: (qmail 93073 invoked by uid 500); 14 Sep 2009 15:01:48 -0000 Mailing-List: contact user-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: user@geronimo.apache.org List-Id: Delivered-To: mailing list user@geronimo.apache.org Received: (qmail 93041 invoked by uid 99); 14 Sep 2009 15:01:48 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Sep 2009 15:01:48 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of kevan.miller@gmail.com designates 209.85.211.179 as permitted sender) Received: from [209.85.211.179] (HELO mail-yw0-f179.google.com) (209.85.211.179) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Sep 2009 15:01:39 +0000 Received: by ywh9 with SMTP id 9so4348300ywh.32 for ; Mon, 14 Sep 2009 08:01:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:content-type:mime-version :subject:from:in-reply-to:date:content-transfer-encoding:message-id :references:to:x-mailer; bh=ZzLR7Wee/I8HEw2jAbTcVyjeWKv7szCPFV+8M8IhbLE=; b=kmcyJZ5WWWiXH2b9d/yucGmwXf6OFMQnSoL8SEnmeXeHw5iIcJFIoeDqkKlo5Lwgs5 kuuDqYJ7i4BUg+dPj5ZC6CdrTzwof7xHc0KtJeMhrQAGiyf5+ICyRA8Q38rUqXfdvopy HQ2yX6YBTAkf453rKQYWhdlMUIO9lSJR84Xx0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; b=rpOWD3ZjgXErE8gUxPvs6VbQePhR+DOTMEABEt0HqDR+uy3u1O/yxUySEWSwCu768q 4v0L2EPAD+8OVzEN//hgP4+Ee2MyeZy+yXQzaLuZoG8NmW10CoGe8bwDDxFKeMET6C+F Oz/kN7/1bWUs2uTVJ2tKKI03NmofK3owFCUSM= Received: by 10.90.45.19 with SMTP id s19mr3911573ags.100.1252940478495; Mon, 14 Sep 2009 08:01:18 -0700 (PDT) Received: from coltrane-009027039226.raleigh.ibm.com (bi01p1.nc.us.ibm.com [129.33.49.251]) by mx.google.com with ESMTPS id 9sm3116597agb.79.2009.09.14.08.01.17 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 14 Sep 2009 08:01:17 -0700 (PDT) Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes Mime-Version: 1.0 (Apple Message framework v1076) Subject: Re: Starting Geronimo with More PermGen From: Kevan Miller In-Reply-To: <69BEFCE5AAEBCA44B1301AD2360E83C7A64DB20A02@MATSVEC14.mclane.local> Date: Mon, 14 Sep 2009 11:01:16 -0400 Content-Transfer-Encoding: 7bit Message-Id: References: <1f3854d50909110652w2d71f1b9x246a74b35cc4aa4e@mail.gmail.com> <3B5690A1-0E26-4C93-B36F-DE44650C49DD@gmail.com> <1f3854d50909110856g7d9761bbg12f006e8bd3cbc16@mail.gmail.com> <69BEFCE5AAEBCA44B1301AD2360E83C7A64DB2091A@MATSVEC14.mclane.local> <1f3854d50909130515m7e5dc2d6oc113215fb57dea70@mail.gmail.com> <69BEFCE5AAEBCA44B1301AD2360E83C7A64DB20A02@MATSVEC14.mclane.local> To: user@geronimo.apache.org X-Mailer: Apple Mail (2.1076) X-Virus-Checked: Checked by ClamAV on apache.org On Sep 14, 2009, at 9:59 AM, Russell Collins wrote: > The main issue with permgen that I have had is with continuous build > processes. At the end of my continuous build process, the artifacts > are deployed to the server. After about 10 or so deployments, the > permgen issue arises without fail. What ends up happening is that > the Geronimo server needs to be restarted. This memory leak/hogging/ > etc does not happen when Geronimo uses JRockit. Russell, Is your build process undeploying the artifacts? If your artifacts are being undeployed and over time you run out of PermGen, then there's a ClassLoader memory leak. Could be in Geronimo or in application/ application library code. Using JRockit, you're moving the memory leak from a specialized PermGen space, to a generalized Heap space (which is larger and thus you're less likely to run out of memory). Either way, you still have a memory leak... Using Sun JDK, if you run with -XX:+HeapDumpOnOutOfMemoryError you'll generate a java_pid.hprof file. This file can be used to diagnose your problem. We can help, if you collect this data and post it to a Jira. --kevan