You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Oliver Sauder (JIRA)" <ji...@apache.org> on 2011/09/02 18:53:10 UTC

[jira] [Updated] (BEANUTILS-399) MappedMethodReference does not reconstruct method the same way MappedPropertyDescriptor does

     [ https://issues.apache.org/jira/browse/BEANUTILS-399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Oliver Sauder updated BEANUTILS-399:
------------------------------------

    Summary: MappedMethodReference does not reconstruct method the same way MappedPropertyDescriptor does  (was: In case of Memory Leak MappedMethodReference does not reconstruct method the same way MappedPropertyDescriptor does)

> MappedMethodReference does not reconstruct method the same way MappedPropertyDescriptor does
> --------------------------------------------------------------------------------------------
>
>                 Key: BEANUTILS-399
>                 URL: https://issues.apache.org/jira/browse/BEANUTILS-399
>             Project: Commons BeanUtils
>          Issue Type: Bug
>          Components: Bean / Property Utils
>    Affects Versions: 1.8.3
>         Environment: OpenJDK 64-Bit Server VM (build 19.0-b09, mixed mode)
>            Reporter: Oliver Sauder
>            Priority: Critical
>             Fix For: 1.8.4
>
>         Attachments: fix-reconstruction-of-lost-method.patch
>
>
> In case the MappedMethodReference has lost its reference due to garbage collection the reconstruction only works for methods which have the exact parameter types. In other cases a RuntimeException is thrown.
> However when MappedPropertyDescriptor creates such a MappedMethodReference it also finds methods which are compatible for given types.
> Marking critical as under high load this bug can occur and stop the system from working as expected.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira