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] [Commented] (MYFACES-4049) JSF myfaces unsynchronized access to a WeakHashMap
Date Tue, 07 Jun 2016 18:14:20 GMT

    [ https://issues.apache.org/jira/browse/MYFACES-4049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15319048#comment-15319048
] 

Bill Lucy commented on MYFACES-4049:
------------------------------------

I've tested the patch locally, and it looks fine to me; this makes sense.

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