You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Igor Vaynberg (JIRA)" <ji...@apache.org> on 2010/08/14 08:43:17 UTC

[jira] Resolved: (WICKET-1082) Check for concurrent access to HashMaps and other data structures

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

Igor Vaynberg resolved WICKET-1082.
-----------------------------------

      Assignee: Igor Vaynberg
    Resolution: Won't Fix

too broad

> Check for concurrent access to HashMaps and other data structures
> -----------------------------------------------------------------
>
>                 Key: WICKET-1082
>                 URL: https://issues.apache.org/jira/browse/WICKET-1082
>             Project: Wicket
>          Issue Type: Task
>    Affects Versions: 1.3.0-beta4
>            Reporter: Jonathan Locke
>            Assignee: Igor Vaynberg
>             Fix For: 1.5-M2
>
>
> We just found and fixed a serious concurrency issue in Localizer.  The HashMap in Localizer is accessed concurrently and under a high enough load, sometimes the HashMap data structure gets corrupted, causing infinite loops on servers.  We need to ensure that other places don't have this problem too.  Any application scope shared data structure (shared resources maybe?) should be checked and made concurrent for 1.3 final, if possible.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.