myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Lucy (JIRA)" <...@myfaces.apache.org>
Subject [jira] [Updated] (MYFACES-4049) JSF myfaces unsynchronized access to a WeakHashMap
Date Mon, 13 Jun 2016 19:11:30 GMT

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

Bill Lucy updated MYFACES-4049:
-------------------------------
       Resolution: Fixed
         Assignee: Bill Lucy
    Fix Version/s: 2.2.11
                   2.1.19
                   2.0.25
           Status: Resolved  (was: Patch Available)

Went ahead and committed this patch; thanks Eduardo Breijo!

> 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
>    Affects Versions: 2.0.24, 2.2.10
>            Reporter: Eduardo Breijo
>            Assignee: Bill Lucy
>             Fix For: 2.0.25, 2.1.19, 2.2.11
>
>         Attachments: MYFACES-4049.patch
>
>
> 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)

Mime
View raw message