commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pelladi Gabor (JIRA)" <>
Subject [jira] [Updated] (OGNL-224) Performance - Locking and performance problem with OgnlRuntime.findParameterTypes
Date Fri, 19 Oct 2012 08:36:11 GMT


Pelladi Gabor updated OGNL-224:

    Attachment: OGNL-224.patch

Patch to fix this issue
> Performance - Locking and performance problem with OgnlRuntime.findParameterTypes
> ---------------------------------------------------------------------------------
>                 Key: OGNL-224
>                 URL:
>             Project: Commons OGNL
>          Issue Type: Improvement
>          Components: Core Runtime
>    Affects Versions: 3.0
>            Reporter: Pelladi Gabor
>            Priority: Minor
>              Labels: patch, perfomance
>         Attachments: OGNL-224.patch
> 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
> 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:
> 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:

View raw message