You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Leonardo Uribe (Resolved) (JIRA)" <de...@myfaces.apache.org> on 2012/02/25 17:11:49 UTC
[jira] [Resolved] (MYFACES-3474) [perf] LifecycleProviderFactory
does not cache created Factory
[ https://issues.apache.org/jira/browse/MYFACES-3474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Leonardo Uribe resolved MYFACES-3474.
-------------------------------------
Resolution: Fixed
Fix Version/s: 2.1.7
2.0.13
1.2.12
> [perf] LifecycleProviderFactory does not cache created Factory
> --------------------------------------------------------------
>
> Key: MYFACES-3474
> URL: https://issues.apache.org/jira/browse/MYFACES-3474
> Project: MyFaces Core
> Issue Type: Bug
> Affects Versions: 2.0.12, 2.1.6
> Reporter: Martin Kočí
> Assignee: Martin Kočí
> Fix For: 1.2.12, 2.0.13, 2.1.7
>
> Attachments: MYFACES-3474.patch
>
>
> It seems that
> org.apache.myfaces.config.ManagedBeanBuilder.buildManagedBean(FacesContext, ManagedBean) tries to locale implementation of a interface, but the instance found is never stored in application map: see code in org.apache.myfaces.config.annotation.LifecycleProviderFactory.getLifecycleProviderFactory(ExternalContext)
> this lead to Webappclassloader.loadClass invocation, which is sychronized and accesses disk.
> Can significantly affect perfomance of myfaces app with managed-bean in multithreaded environment.
> maybe reason for http://prezi.com/dr3on1qcajzw/www-world-wide-wait-devoxx-edition/ ?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira