[
https://issues.apache.org/jira/browse/TOMAHAWK-1170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12631597#action_12631597
]
Leonardo Uribe commented on TOMAHAWK-1170:
------------------------------------------
Tomahawk 1.1.7 has now a solution for avoid configure ExtensionsFilter using a
TomahawkFacesContextWrapper. The best you can do is disable extensionsFilter
checking and TomahawkFacesContextWrapper
<context-param>
<param-name>org.apache.myfaces.CHECK_EXTENSIONS_FILTER</param-name>
<param-value>false</param-value>
</context-param>
<context-param>
<param-name>org.apache.myfaces.DISABLE_TOMAHAWK_FACES_CONTEXT_WRAPPER</param-name>
<param-value>true</param-value>
</context-param>
The default behavior is if ExtensionsFilter is not configured, it try to use
TomahawkFacesContextWrapper as alternative, but since the checking of
extensions filter is enabled by default it throws the exception when try to use
it.
> Resource mapping missing / throwExtensionsFilterMissing reported incorrectly
> under load
> ---------------------------------------------------------------------------------------
>
> Key: TOMAHAWK-1170
> URL: https://issues.apache.org/jira/browse/TOMAHAWK-1170
> Project: MyFaces Tomahawk
> Issue Type: Bug
> Components: ExtensionsFilter
> Affects Versions: 1.1.7-SNAPSHOT
> Reporter: Simon Kitching
>
> It has been reported by two users that under load an application using
> Tomahawk intermittently throws an exception claiming "resource mapping
> missing".
> This message is meant to be thrown when a component in a request wants to
> register stuff for the extensions filter to output, but the current request
> never passed through the extensions filter. This is a sanity check to ensure
> that people that misconfigure the ExtensionsFilter get a helpful error
> message rather than just having tomahawk components that need additional
> resources acting weirdly.
> A workaround is to disable this safety check. The first reporter of this
> problem did disable the check and found the issue disappeared.
> The problem appears to be a race condition between multiple threads *reading*
> a map; at least that was the only piece of code I found that had any obvious
> thread race issues. I can't remember the exact piece of code for the moment,
> but will update this issue when I find it again.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
