You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-dev@portals.apache.org by "David Sean Taylor (JIRA)" <je...@portals.apache.org> on 2014/06/02 17:20:01 UTC
[jira] [Resolved] (JS2-1294) Concurrency Issue with
SessionPathResolverCache
[ https://issues.apache.org/jira/browse/JS2-1294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Sean Taylor resolved JS2-1294.
------------------------------------
Resolution: Fixed
applied patch from Joachim. Replaced SynchronizedMap with ConcurrentHashMap
> Concurrency Issue with SessionPathResolverCache
> -----------------------------------------------
>
> Key: JS2-1294
> URL: https://issues.apache.org/jira/browse/JS2-1294
> Project: Jetspeed 2
> Issue Type: Bug
> Components: Components Core
> Affects Versions: 2.2.0, 2.2.1, 2.2.2
> Environment: websphere, IBM Java
> Reporter: Joachim Mueller
> Assignee: David Sean Taylor
> Fix For: 2.3.0
>
> Attachments: JS2-1294.patch
>
>
> A race condition can occur in SessionPathResolverCache since the internal cache is initialized with a non-threadsave HashMap.
> Under websphere we can observe blocking threads while accessing the map at:
> ...
> at java/util/HashMap.findNonNullKeyEntry(HashMap.java:601(Compiled Code))
> at java/util/HashMap.getEntry(HashMap.java:585(Compiled Code))
> at java/util/HashMap.get(HashMap.java:571(Compiled Code))
> at org/apache/jetspeed/decoration/caches/HashMapPathResolverCache.getPath(HashMapPathResolverCache.java:49(Compiled Code))
> ...
> The base class HashMapPathResolverCache is not used and can be removed completely, all methods can be migrated to SessionPathResolverCache.
> Additional a spelling typo has been fixed.
> patch follows...
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org