You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Jonathan Locke (JIRA)" <ji...@apache.org> on 2007/10/18 18:21:50 UTC
[jira] Created: (WICKET-1082) Check for concurrent access to
HashMaps and other data structures
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
Fix For: 1.3.0-beta5
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.
[jira] Updated: (WICKET-1082) Check for concurrent access to
HashMaps and other data structures
Posted by "Igor Vaynberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-1082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Igor Vaynberg updated WICKET-1082:
----------------------------------
Fix Version/s: (was: 1.3.3)
1.5-M1
> 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
> Fix For: 1.5-M1
>
>
> 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.
[jira] Commented: (WICKET-1082) Check for concurrent access to
HashMaps and other data structures
Posted by "Johan Compagner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-1082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12539995 ]
Johan Compagner commented on WICKET-1082:
-----------------------------------------
i found and fixed a few others:
Localizer: cache = new ConcurrentHashMap(); (in clearCache)
AbstractDecimalConverter, the numberFormats cache
EnumeratedType, valuelistbyclass
TimeMap.source
and the modificationwatcher...
> 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
> Fix For: 1.3.0-rc1
>
>
> 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.
[jira] Updated: (WICKET-1082) Check for concurrent access to
HashMaps and other data structures
Posted by "Frank Bille Jensen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-1082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Frank Bille Jensen updated WICKET-1082:
---------------------------------------
Fix Version/s: (was: 1.3.0-rc2)
1.3.0-rc3
> 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
> Fix For: 1.3.0-rc3
>
>
> 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.
[jira] Updated: (WICKET-1082) Check for concurrent access to
HashMaps and other data structures
Posted by "Igor Vaynberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-1082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Igor Vaynberg updated WICKET-1082:
----------------------------------
Fix Version/s: 1.5-M2
(was: 1.5-M1)
> 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
> 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.
[jira] Updated: (WICKET-1082) Check for concurrent access to
HashMaps and other data structures
Posted by "Frank Bille Jensen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-1082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Frank Bille Jensen updated WICKET-1082:
---------------------------------------
Fix Version/s: (was: 1.3.0-rc1)
1.3.0-rc2
> 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
> Fix For: 1.3.0-rc2
>
>
> 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.
[jira] Commented: (WICKET-1082) Check for concurrent access to
HashMaps and other data structures
Posted by "Martijn Dashorst (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-1082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536019 ]
Martijn Dashorst commented on WICKET-1082:
------------------------------------------
Doesn't findbugs discover these uses? We should run it, and PMD as well to check for these kind of discrepancies.
findbugs: http://findbugs.sourceforge.net/
pmd: http://pmd.sourceforge.net
> 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
> Fix For: 1.3.0-beta5
>
>
> 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.
[jira] Updated: (WICKET-1082) Check for concurrent access to
HashMaps and other data structures
Posted by "Frank Bille Jensen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-1082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Frank Bille Jensen updated WICKET-1082:
---------------------------------------
Fix Version/s: (was: 1.3.2)
1.3.3
> 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
> Fix For: 1.3.3
>
>
> 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.
[jira] Resolved: (WICKET-1082) Check for concurrent access to
HashMaps and other data structures
Posted by "Igor Vaynberg (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (WICKET-1082) Check for concurrent access to
HashMaps and other data structures
Posted by "Frank Bille Jensen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-1082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Frank Bille Jensen updated WICKET-1082:
---------------------------------------
Fix Version/s: (was: 1.3.0-rc3)
1.3.1
> 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
> Fix For: 1.3.1
>
>
> 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.
[jira] Updated: (WICKET-1082) Check for concurrent access to
HashMaps and other data structures
Posted by "Frank Bille Jensen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-1082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Frank Bille Jensen updated WICKET-1082:
---------------------------------------
Fix Version/s: (was: 1.3.1)
1.3.2
> 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
> Fix For: 1.3.2
>
>
> 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.