You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Mark Yvanovich (JIRA)" <de...@myfaces.apache.org> on 2012/10/04 17:03:48 UTC

[jira] [Updated] (TRINIDAD-2326) Don't permanently cache the null resource loader

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

Mark Yvanovich updated TRINIDAD-2326:
-------------------------------------

    Status: Patch Available  (was: Open)
    
> Don't permanently cache the null resource loader
> ------------------------------------------------
>
>                 Key: TRINIDAD-2326
>                 URL: https://issues.apache.org/jira/browse/TRINIDAD-2326
>             Project: MyFaces Trinidad
>          Issue Type: Bug
>          Components: Infrastructure
>    Affects Versions:  1.2.12-core, 2.0.1-core, 2.1.0-core
>            Reporter: Mark Yvanovich
>         Attachments: jira2326-trunk.patch
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> In ResourceServlet._getResourceLoader(), if an exception occurs while getting the resource loader, we use the null resource loader and this loader is cached so from that point on we return null for any resource request with the specified servlet path that caused the exception.  We want to make this a bit more fault tolerant so we are going to implement a exponential backoff resource loader to be used in place of the null resource loader.  This loader will periodically re-attempt to load the resource loader for the specified servlet path and replace the exponential backoff resource loader in ResourceServlet's loader cache if it is found so that subsequent requests will succeed.

--
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