Return-Path: X-Original-To: apmail-commons-issues-archive@minotaur.apache.org Delivered-To: apmail-commons-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0910FD700 for ; Thu, 13 Dec 2012 07:33:22 +0000 (UTC) Received: (qmail 49938 invoked by uid 500); 13 Dec 2012 07:33:21 -0000 Delivered-To: apmail-commons-issues-archive@commons.apache.org Received: (qmail 49757 invoked by uid 500); 13 Dec 2012 07:33:21 -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 49745 invoked by uid 99); 13 Dec 2012 07:33:21 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Dec 2012 07:33:21 +0000 Date: Thu, 13 Dec 2012 07:33:21 +0000 (UTC) From: "Lukasz Lenart (JIRA)" To: issues@commons.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (OGNL-228) Is ognl.OgnlRuntime some root cause of PermGen OutOfMemoryError problem? 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/OGNL-228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13530759#comment-13530759 ] Lukasz Lenart commented on OGNL-228: ------------------------------------ No, just changes between 3.0.5 and 3.0.6 are mainly touching performance and some rase conditions and basically the whole 3.0.x is just a maintenance with no breaking changes. > Is ognl.OgnlRuntime some root cause of PermGen OutOfMemoryError problem? > ------------------------------------------------------------------------ > > Key: OGNL-228 > URL: https://issues.apache.org/jira/browse/OGNL-228 > Project: Commons OGNL > Issue Type: Bug > Environment: RHEL 6 x64 > Reporter: haruhiko nishi > Priority: Critical > Labels: OutOfMemoryError > > While analyzing several heap dumps using Yourkit, we have observed many instances of DelegatingClassLoader, or more precisely sun.reflect.GeneratedMethodAccessorXXX, where XXX represents some sequential numbers, were created through the usage of Java reflection by the frameworks implemented in our web application. > GeneratedMethodAccessorXXX is allegedly used for some sort of reflection optimization mechanism according to the url at http://www-01.ibm.com/support/docview.wss?uid=swg21566549. > Because this is what seems to be eating up our memory allocated for PermGen, as the number of the DelegatingClassLoader is gradually increased and JVM crushes with OutOfMemoryError, we scrutinized what is possibly blocking these DelegatingClassLoaders from being garbage collected and found many of them are relevant to _methodParameterTypesCache of ognl.OgnlRuntime. > Is there any known problems regarding this issue? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira