You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@myfaces.apache.org by "Eduardo Breijo (JIRA)" <de...@myfaces.apache.org> on 2016/06/06 16:19:21 UTC

[jira] [Updated] (MYFACES-4049) JSF myfaces unsynchronized access to a WeakHashMap

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

Eduardo Breijo updated MYFACES-4049:
------------------------------------
    Status: Patch Available  (was: Open)

> JSF myfaces unsynchronized access to a WeakHashMap 
> ---------------------------------------------------
>
>                 Key: MYFACES-4049
>                 URL: https://issues.apache.org/jira/browse/MYFACES-4049
>             Project: MyFaces Core
>          Issue Type: Bug
>            Reporter: Eduardo Breijo
>
> WebContainer threads are hanging due to a thread safety issue in the underlying JSF 2.0 code. A non thread-safe WeakHashMap is being used in the getRelativePath method of the DefaultFacelet class. Apache JSF 2.0 code is not synchronizing on their usage of WeakHashMap in
> org.apache.myfaces.view.facelets.impl.DefaultFacelet.getRelativePath. 
> In order to make the code thread-safe Collections.synchronizedMap method needs to be used.
> A patch has been provided.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)