[
https://issues.apache.org/jira/browse/OGNL-228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13530895#comment-13530895
]
haruhiko nishi commented on OGNL-228:
-------------------------------------
We are seeing thousands of ognl.OgnlRunTime in the path to the classloader as
depicted above. So my question is if this is the consequence of some
misconfiguration or it is how it supposed to be.
> 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
