[
https://issues.apache.org/jira/browse/OGNL-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13483037#comment-13483037
]
Pelladi Gabor commented on OGNL-224:
------------------------------------
Thank you. Monday and Tuesday were a national holiday in Hungary, that is why I
did not read your answer until today.
By the way, is there any plan to release OGNL 4.0, and Struts2 depending on
OGNL 4.0? I have seen some activity in 2011, but this year not so much.
> Performance - Locking and performance problem with
> OgnlRuntime.findParameterTypes
> ---------------------------------------------------------------------------------
>
> Key: OGNL-224
> URL: https://issues.apache.org/jira/browse/OGNL-224
> Project: Commons OGNL
> Issue Type: Improvement
> Components: Core Runtime
> Affects Versions: 3.0
> Reporter: Pelladi Gabor
> Assignee: Lukasz Lenart
> Priority: Minor
> Labels: patch, perfomance
> Fix For: 3.0
>
> Attachments: OGNL-224.patch, OgnlRuntimeTest.java
>
>
> I am using struts2 and under heavy load (around 100 threads) many threads are
> in BLOCKED state because of OgnlRuntime.findParameterTypes(). The actions we
> use have a generic superclass like:
> public class PersonalCaptureAction extends DataCaptureAction<PersonalDTO>
> OGNL handles this very bad, it enters
> synchronized (_genericMethodParameterTypesCache)
> all the time, at every property access of the Action. A possible workaround
> is to introduce another layer of superclass that is not generic.
> I know that in current OGNL trunk (4.0-SNAPSHOT) caching has been rewritten,
> but Struts2 is using 3.0.5, and maybe it could be fixed as 3.0.6 in the git
> tree I found:
> https://github.com/jkuhnert/ognl
> I will attach a patch and a testcase.
--
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
