You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Emmanuel Lecharny (JIRA)" <di...@incubator.apache.org> on 2005/11/21 17:18:41 UTC
[jira] Resolved: (DIRLDAP-71) CachingNormalizer exhibits concurrency flaw under load.
[ http://issues.apache.org/jira/browse/DIRLDAP-71?page=all ]
Emmanuel Lecharny resolved DIRLDAP-71:
--------------------------------------
Resolution: Fixed
Assign To: Emmanuel Lecharny
- Some tests have been added to avoid NPE
- the LRUMap is now synchronized
- the cacheNormalizer is now threadsafe.
> CachingNormalizer exhibits concurrency flaw under load.
> -------------------------------------------------------
>
> Key: DIRLDAP-71
> URL: http://issues.apache.org/jira/browse/DIRLDAP-71
> Project: Directory LDAP
> Type: Bug
> Components: Common
> Versions: 0.9.3
> Reporter: Jacob S. Barrett
> Assignee: Emmanuel Lecharny
> Attachments: CachingNormalizer-Concurrency.patch
>
> CachingNormalizer doesn't have it's cache protected from concurrent modifications. Under load a state is reached where cache.containsKey(key) is true but the result of cache.get(key) results in an unexpected null value and thus a NullPointerException. This is really only reached when you have more than threads than the max cache size and therefore items in the cache are being purged. The attached path synchronizes the cache. It would be better to use a R/W lock from JSR 166 backport or something similar.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira